CVE-2026-42864: FireFighter has unauthenticated SSRF in its Raid jira_bot endpoint that allows IAM credential theft

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 0.4%, percentile 38: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 38% of all scored CVEs (low). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes firefighter-incident (PyPI) < 0.0.54, fixed in 0.0.54. Check your lockfile, including transitive dependencies.

What it is

FireFighter is an incident management application. Prior to 0.0.54, the POST /api/v2/firefighter/raid/jirabot endpoint (CreateJiraBotView) is reachable without authentication (permissionclasses = [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 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. This vulnerability is fixed in 0.0.54.

From the GitHub advisory

Impact The POST /api/v2/firefighter/raid/jirabot endpoint (CreateJiraBotView) is reachable without authentication (permissionclasses = [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.addattachmentstoissue

### 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.

Weakness type: CWE-306, CWE-918.

Product: firefighter-incident (PyPI) · Assigned by: GitHub_M · Published: 2026-05-11

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact partial.
• FIRST EPSS (model of 2026-10-21): 0.45% probability of exploitation activity in the next 30 days; percentile 38.

Timeline

• 2026-05-05 — GitHub-reviewed advisory GHSA-fqvv-jvhr-g5jc published (critical)
• 2026-05-11 — CVE record last updated
• 2026-05-11 — CVE record published by GitHub_M

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-fqvv-jvhr-g5jc github.com
2. CVE.org record CVE-2026-42864 cve.org
3. NVD entry CVE-2026-42864 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com

Critical PyPI advisories · Today’s Security Digest