CVE-2026-77249: CWE-918: Server-Side Request Forgery (SSRF) in sooperset mcp-atlassian
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, JiraUserMixin._lookup_user_by_permissions uses the module-level requests.get function instead of the fetcher's protected session. A caller-controlled public Jira URL can redirect that unhooked request to an internal address, bypassing the redirect checks added for CVE-2026-27826. The advisory traces the vulnerable input and processing flow through JiraUserMixin._lookup_user_by_permissions, requests.get, self.jira._session.get, and _make_ssrf_safe_hook, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
AI Analysis
Technical Summary
The vulnerability in sooperset mcp-atlassian (CVE-2026-77249) involves improper handling of HTTP requests in the JiraUserMixin._lookup_user_by_permissions method. Before version 0.22.0, this method uses the unprotected requests.get function rather than the fetcher's protected session, enabling an attacker to supply a public Jira URL that redirects the request to internal network addresses. This bypasses redirect checks implemented for a previous vulnerability (CVE-2026-27826). The issue is traced through the code paths involving requests.get, self.jira._session.get, and _make_ssrf_safe_hook. The vulnerability is resolved in version 0.22.0.
Potential Impact
An attacker can exploit this SSRF vulnerability to cause the server to make unauthorized HTTP requests to internal network resources, potentially exposing sensitive information accessible only within the internal network. The impact is limited to information disclosure (confidentiality loss) with no integrity or availability impact reported. The CVSS score of 5.3 reflects a medium severity.
Mitigation Recommendations
Upgrade sooperset mcp-atlassian to version 0.22.0 or later, where the vulnerability is fixed by using the fetcher's protected session for HTTP requests instead of the unprotected requests.get function. No other mitigations are specified or required.
CVE-2026-77249: CWE-918: Server-Side Request Forgery (SSRF) in sooperset mcp-atlassian
Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, JiraUserMixin._lookup_user_by_permissions uses the module-level requests.get function instead of the fetcher's protected session. A caller-controlled public Jira URL can redirect that unhooked request to an internal address, bypassing the redirect checks added for CVE-2026-27826. The advisory traces the vulnerable input and processing flow through JiraUserMixin._lookup_user_by_permissions, requests.get, self.jira._session.get, and _make_ssrf_safe_hook, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
CVSS v3.1
Score 5.3medium
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
The vulnerability in sooperset mcp-atlassian (CVE-2026-77249) involves improper handling of HTTP requests in the JiraUserMixin._lookup_user_by_permissions method. Before version 0.22.0, this method uses the unprotected requests.get function rather than the fetcher's protected session, enabling an attacker to supply a public Jira URL that redirects the request to internal network addresses. This bypasses redirect checks implemented for a previous vulnerability (CVE-2026-27826). The issue is traced through the code paths involving requests.get, self.jira._session.get, and _make_ssrf_safe_hook. The vulnerability is resolved in version 0.22.0.
Potential Impact
An attacker can exploit this SSRF vulnerability to cause the server to make unauthorized HTTP requests to internal network resources, potentially exposing sensitive information accessible only within the internal network. The impact is limited to information disclosure (confidentiality loss) with no integrity or availability impact reported. The CVSS score of 5.3 reflects a medium severity.
Mitigation Recommendations
Upgrade sooperset mcp-atlassian to version 0.22.0 or later, where the vulnerability is fixed by using the fetcher's protected session for HTTP requests instead of the unprotected requests.get function. No other mitigations are specified or required.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-20T19:02:23.416Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ab2d108f7a7c541069ead03
Added to database: 09/22/2026, 19:03:36 UTC
Last enriched: 09/22/2026, 19:18:23 UTC
Last updated: 09/22/2026, 20:07:39 UTC
Views: 4
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.