NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

FireFighter has unauthenticated SSRF in its Raid jira_bot endpoint that allows IAM credential theftGHSA-fqvv-jvhr-g5jc

CRITICALFix: ManoManoTech/firefighter-incident@2586679

GHSA-fqvv-jvhr-g5jc is a critical-severity (CVSS 9.9) Missing Authentication vulnerability in firefighter-incident. A fix is available for firefighter-incident — see the affected versions and patch details below.

Also known asCVE-2026-42864PYSEC-2026-339
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fqvv-jvhr-g5jc.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs20th percentile — riskier than 20% of all scored CVEsHighest risk
0.00%0.32%0.63%0.95%0.1%0.3%Jun 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍firefighter-incident

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIfirefighter-incidentall versions0.0.54pip install --upgrade 'firefighter-incident==0.0.54'

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for firefighter-incident, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update firefighter-incident to 0.0.54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fqvv-jvhr-g5jc is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

### 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 d
O3 Security · Impact-Aware SCA

Is GHSA-fqvv-jvhr-g5jc in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
FireFighter has unauthenticated SSRF in its Raid jira_bot…