Atlassian
CVE-2026-42864
CRITICAL
GHSA-fqvv-jvhr-g5jc
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 05, 2026
Server-side request forgery combined with missing authentication in firefighter-incident Python package allows unauthenticated remote attackers to exfiltrate AWS IAM credentials from cloud metadata endpoints. The /api/v2/firefighter/raid/jira_bot endpoint accepts arbitrary URLs in the attachments parameter, fetches them server-side without validation, and uploads responses as Jira attachments — enabling SSRF against internal services including http://169.254.169.254/ (AWS EC2 Instance Metadata Service). Vendor-released patch (version 0.0.54) enforces authentication and validates attachment URLs to block private/link-local/loopback addresses. No public exploit identified at time of analysis, but exploitation is trivial given detailed advisory with exact vulnerable code paths.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in pypi
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Know when Atlassian gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L
Primary rating from Vendor (https://github.com/ManoManoTech/firefighter-incident) · only source for this CVE.
CVSS VectorVendor: https://github.com/ManoManoTech/firefighter-incident
DescriptionCVE.org
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-CreateJiraBotViewsrc/firefighter/raid/serializers.py-LandbotIssueRequestSerializer.attachmentssrc/firefighter/raid/client.py-RaidJiraClient.add_attachments_to_issue
Patches
Fixed in firefighter-incident 0.0.54:
CreateJiraBotViewnow enforcesBearerTokenAuthentication+IsAuthenticated.attachmentsURLs 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_botto 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=1on 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
Executive ViewAI
The firefighter-incident Python package contains a critical server-side request forgery vulnerability that allows unauthenticated attackers to exfiltrate AWS IAM credentials from EC2 instance metadata services. Organizations running this package in AWS environments face immediate risk of cloud credential compromise, which could enable lateral movement, data exfiltration, and infrastructure takeover. This vulnerability requires urgent patching as the attack requires no authentication and minimal technical sophistication.
Within 24 hours: Identify all deployments of firefighter-incident package and confirm current version; immediately restrict network access to the /api/v2/firefighter/raid/jira_bot endpoint via WAF or firewall rules. Within 7 days: Apply vendor patch to version 0.0.54 or later across all affected systems; validate patch deployment and confirm authentication enforcement on the vulnerable endpoint. Within 30 days: Conduct credential audit to identify any AWS IAM credentials that may have been accessed via metadata endpoint; rotate all credentials in affected EC2 instances; implement network segmentation to restrict metadata service access only to authorized processes.
Apply vendor patch. If immediate patching is not feasible: (1) disable or restrict network access to the /api/v2/firefighter/raid/jira_bot endpoint via WAF/firewall rules; (2) implement IAM instance profiles with minimal permissions and assume role-based credentials instead of long-lived keys; (3) block outbound HTTP/HTTPS from the application to private IP ranges including 169.254.0.0/16 and 10.0.0.0/8 at the network layer; (4) monitor CloudTrail and application logs for suspicious metadata endpoint requests.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)CVE.org
Atlassian has been made aware of an issue reported by a handful of customers where external attackers may have exploited
The HipChat for JIRA plugin before 6.30.0 for Atlassian JIRA allows remote authenticated users to execute arbitrary Java
Atlassian Confluence before 5.8.17 allows remote authenticated users to read configuration files via the decoratorName p
Atlassian JIRA before 5.0.1; Confluence before 3.5.16, 4.0 before 4.0.7, and 4.1 before 4.1.10; FishEye and Crucible bef
Directory traversal vulnerability in the Issue Collector plugin in Atlassian JIRA before 6.0.4 allows remote attackers t
All versions of Confluence Data Center and Server are affected by this unexploited vulnerability. Rated critical severit
There is a command injection vulnerability using environment variables in Bitbucket Server and Data Center. Rated critic
In affected versions of Confluence Server and Data Center, an OGNL injection vulnerability exists that would allow an un
Atlassian Crowd and Crowd Data Center had the pdkinstall development plugin incorrectly enabled in release builds. Rated
The IconUriServlet of the Atlassian OAuth Plugin from version 1.3.0 before version 1.9.12 and from version 2.0.0 before
This High severity RCE (Remote Code Execution) vulnerability was introduced in version 5.2 of Confluence Data Center and
Multiple API endpoints in Atlassian Bitbucket Server and Data Center 7.0.0 before version 7.6.17, from version 7.7.0 bef
Exploit-DB