critical · 9.9 Patched

FireFighter has unauthenticated SSRF in its Raid jira_bot endpoint that allows IAM credential theft

CVE-2026-42864 · GHSA-fqvv-jvhr-g5jc · PYSEC-2026-339 · published 5 May 2026

How serious is it

  • Severity: critical, CVSS score 9.9 out of 10.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2026-42864?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • firefighter-incident (PyPI) < 0.0.54

How to check

  1. Run pip show firefighter-incident in your project to see the installed version, including copies pulled in by other packages.
  2. Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.
  3. Or run npx shippable-dev scan localhost:3000 in your project folder. It reads your lockfile and flags this vulnerability along with every other known one.

How to fix

Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
  1. Upgrade firefighter-incident to 0.0.54 or later, commit the lockfile and redeploy.
  2. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

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

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from GitHub Advisory Database, OSV. Last updated 28 Oct 2026. All vulnerabilities · RSS · JSON

Get alerts for new exploited vulnerabilities