GHSA-fqvv-jvhr-g5jc

Suggest an improvement
Source
https://github.com/advisories/GHSA-fqvv-jvhr-g5jc
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-fqvv-jvhr-g5jc/GHSA-fqvv-jvhr-g5jc.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-fqvv-jvhr-g5jc
Aliases
  • CVE-2026-42864
Published
2026-05-05T18:21:17Z
Modified
2026-05-13T14:33:54.359866Z
Severity
  • 9.9 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L CVSS Calculator
Summary
FireFighter has unauthenticated SSRF in its Raid jira_bot endpoint that allows IAM credential theft
Details

Impact

The POST /api/v2/firefighter/raid/jira_bot endpoint (CreateJiraBotView) is reachable without authentication (permission_classes = [permissions.AllowAny]). Its attachments payload is fetched server-side via httpx.get() with no URL validation, then uploaded as an attachment on the Jira ticket that gets created.

An unauthenticated caller able to reach the ingress can coerce the pod into fetching arbitrary URLs — including the cloud metadata endpoint at http://169.254.169.254/ — and exfiltrate the response as a Jira attachment.

On EC2/EKS deployments that do not enforce IMDSv2, this allows theft of the temporary AWS credentials attached to the pod's IAM role. The docstring on the view claims a Bearer token is required, but the code does not enforce it.

Affected code paths: - src/firefighter/raid/views/__init__.py — CreateJiraBotView - src/firefighter/raid/serializers.py — LandbotIssueRequestSerializer.attachments - src/firefighter/raid/client.py — RaidJiraClient.add_attachments_to_issue

### Patches Fixed in firefighter-incident 0.0.54: - CreateJiraBotView now enforces BearerTokenAuthentication + IsAuthenticated. - attachments URLs are validated: http(s) scheme only, max 10 URLs, rejection of any host resolving to a private, loopback, link-local, reserved, multicast or unspecified IP (IPv4 and IPv6). - Fixes an unrelated KeyError('attachments') surfaced during regression testing.

Users should upgrade to 0.0.54 or later.

### Workarounds Until upgrade is possible, any one of the following blocks end-to-end exploitation: - Restrict ingress access to /api/v2/firefighter/raid/jira_bot to trusted networks only (VPN, internal load balancer). - Rotate or revoke the Jira API token configured as RAID_JIRA_API_PASSWORD; this breaks jira.create_issue() before the vulnerable attachment fetch is reached (legitimate traffic is also blocked — emergency mitigation only). - Enforce IMDSv2 with HttpPutResponseHopLimit=1 on EC2/EKS nodes. This does not fix the SSRF itself but neutralises the IAM-credential-theft path.

### Resources - CWE-918: Server-Side Request Forgery - CWE-306: Missing Authentication for Critical Function

Database specific 
{
    "cwe_ids": [
        "CWE-306",
        "CWE-918"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-05T18:21:17Z",
    "nvd_published_at": "2026-05-11T19:16:24Z",
    "severity": "CRITICAL"
}
References

Affected packages

PyPI / firefighter-incident

Package

Name
firefighter-incident
View open source insights on deps.dev
Purl
pkg:pypi/firefighter-incident

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.0.54

Affected versions

0.*
0.0.1rc1
0.0.1rc2
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8
0.0.9
0.0.10
0.0.11
0.0.12
0.0.13
0.0.14
0.0.15
0.0.16
0.0.17
0.0.18
0.0.19
0.0.20
0.0.21
0.0.22
0.0.23
0.0.24
0.0.25
0.0.26
0.0.27
0.0.28
0.0.29
0.0.30
0.0.31
0.0.32
0.0.33
0.0.34
0.0.35
0.0.36
0.0.37
0.0.38
0.0.39
0.0.40
0.0.41
0.0.42
0.0.43
0.0.44
0.0.45
0.0.46
0.0.47
0.0.48
0.0.49
0.0.50
0.0.51
0.0.52
0.0.53

Database specific

source 
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-fqvv-jvhr-g5jc/GHSA-fqvv-jvhr-g5jc.json"