Skip to main content

Description

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to version 0.17.0, an unauthenticated attacker who can reach the mcp-atlassian HTTP endpoint can force the server process to make outbound HTTP requests to an arbitrary attacker-controlled URL by supplying two custom HTTP headers without an `Authorization` header. No authentication is required. The vulnerability exists in the HTTP middleware and dependency injection layer — not in any MCP tool handler - making it invisible to tool-level code analysis. In cloud deployments, this could enable theft of IAM role credentials via the instance metadata endpoint (`169[.]254[.]169[.]254`). In any HTTP deployment it enables internal network reconnaissance and injection of attacker-controlled content into LLM tool results. Version 0.17.0 fixes the issue.

Key Findings

as of 2026-11-22
All KEV statistics→
  • Its current EPSS score (13.9%) is higher than that of 28% of CISA KEV entries.

Severity

CVSS 3.1 · CNA · Base score8.2 HIGH
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:NOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationpoc
Automatableno
Technical impactpartial

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
60 days
Asset not publicly exposed
Next upgrade
fix on system upgrade

If CISA adds it to the KEV catalog: 14 days on a publicly exposed asset, 14 days on other assets.

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (not listed) and CISA's SSVC values (automatable no, technical impact partial, 2026-03-10).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Fix on system upgrade means remediating the next time the asset receives a scheduled major upgrade or rebuild.

If CISA adds the CVE to the KEV catalog, the timeline shortens.

Affected Products

ProductAffected versions
sooperset
mcp-atlassian
< 0.17.0

References

2 links

Record Details

Published
2026-03-10
Last updated
2026-03-10
Assigner (CNA)
GitHub_M
Credited to
-

More from sooperset

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.