CVE-2026-77265: CWE-918: Server-Side Request Forgery (SSRF) in sooperset mcp-atlassian
CVE-2026-77265 is a Server-Side Request Forgery (SSRF) vulnerability in the MCP Atlassian server component used for Atlassian products like Confluence and Jira. Versions prior to 0.22.0 improperly validate header-supplied Jira or Confluence URLs, allowing an unauthenticated attacker to exploit DNS rebinding to make requests to internal or metadata services. This vulnerability is fixed in version 0.22.0.
AI Analysis
Technical Summary
MCP Atlassian, a Model Context Protocol server for Atlassian products, contains an SSRF vulnerability (CWE-918) in versions before 0.22.0. The issue arises because header-supplied URLs (via X-Atlassian-Jira-Url and X-Atlassian-Confluence-Url) are initially validated against a DNS name that resolves to a public IP but then re-resolved during connection to an internal IP due to DNS rebinding. This allows unauthenticated attackers to bypass validation and send requests to internal or metadata services. The vulnerability is addressed by fixing the URL validation and resolution logic in version 0.22.0.
Potential Impact
An unauthenticated attacker can exploit this SSRF vulnerability to send requests from the MCP Atlassian server to internal network resources or metadata services, potentially exposing sensitive internal information. The CVSS score of 5.9 (medium severity) reflects the network attack vector with high complexity and no privileges required, impacting confidentiality but not integrity or availability.
Mitigation Recommendations
Upgrade MCP Atlassian to version 0.22.0 or later, where this SSRF vulnerability is fixed. No other mitigation is indicated or required according to the advisory.
CVE-2026-77265: CWE-918: Server-Side Request Forgery (SSRF) in sooperset mcp-atlassian
Description
CVE-2026-77265 is a Server-Side Request Forgery (SSRF) vulnerability in the MCP Atlassian server component used for Atlassian products like Confluence and Jira. Versions prior to 0.22.0 improperly validate header-supplied Jira or Confluence URLs, allowing an unauthenticated attacker to exploit DNS rebinding to make requests to internal or metadata services. This vulnerability is fixed in version 0.22.0.
CVSS v3.1
Score 5.9medium
Affected software
sooperset
mcp-atlassian
pkg:github/sooperset/mcp-atlassianRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
MCP Atlassian, a Model Context Protocol server for Atlassian products, contains an SSRF vulnerability (CWE-918) in versions before 0.22.0. The issue arises because header-supplied URLs (via X-Atlassian-Jira-Url and X-Atlassian-Confluence-Url) are initially validated against a DNS name that resolves to a public IP but then re-resolved during connection to an internal IP due to DNS rebinding. This allows unauthenticated attackers to bypass validation and send requests to internal or metadata services. The vulnerability is addressed by fixing the URL validation and resolution logic in version 0.22.0.
Potential Impact
An unauthenticated attacker can exploit this SSRF vulnerability to send requests from the MCP Atlassian server to internal network resources or metadata services, potentially exposing sensitive internal information. The CVSS score of 5.9 (medium severity) reflects the network attack vector with high complexity and no privileges required, impacting confidentiality but not integrity or availability.
Mitigation Recommendations
Upgrade MCP Atlassian to version 0.22.0 or later, where this SSRF vulnerability is fixed. No other mitigation is indicated or required according to the advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-20T19:14:21.330Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ab2c2eff7a7c541068b81df
Added to database: 09/22/2026, 18:03:27 UTC
Last enriched: 09/22/2026, 18:18:19 UTC
Last updated: 09/22/2026, 19:09:09 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.