SSRF via backslash authority confusion
Published Sep 22, 2026 · Updated Sep 22, 2026
SSRF in MCP Atlassian before 0.22.0 allows remote attackers to reach internal services through crafted Atlassian URL headers. The validate_url_for_ssrf function validates the urllib.parse hostname, while Requests interprets a backslash-delimited authority as a different destination. The MCP HTTP endpoint must accept the header-based Jira or Confluence URL flow; successful requests reach loopback or internal services.
Summary
What happened
SSRF in MCP Atlassian before 0.22.0 allows remote attackers to reach internal services through crafted Atlassian URL headers. The validate_url_for_ssrf function validates the urllib.parse hostname, while Requests interprets a backslash-delimited authority as a different destination. The MCP HTTP endpoint must accept the header-based Jira or Confluence URL flow; successful requests reach loopback or internal services.
The record
- CVE
- CVE-2026-77274
- Published
- Sep 22, 2026
- Updated
- Sep 22, 2026
- Vendor
- sooperset
- Product
- MCP Atlassian
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 22, 2026CVE publishedPublication date reported by the CVE source.
- Sep 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.22.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- GHSA-hgcf-4mq8-5266 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started