Skip to main content
VulnerabilityPublished Updated

CVE-2026-32871: Mcp atlassian · FastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerability

Affects mcp-atlassianSource GCVE Database

0
Compare
Authoritative record:CVE-2026-32871· Critical 10.0

Not known to be exploited · CVSS 10.0 Critical : upgrade to 0.23.0 as a priority.

Data as of 30 Oct 2026, 08:31 UTC

CVSS 4.0 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.23.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade mcp-atlassian to 0.23.0.

Affected software

ProductAffectedFixed in
Homebrewmcp-atlassianpkg:brew/mcp-atlassianOther threatsAffected
  • >=0.11.9 <0.23.0
Fixed in
  • 0.23.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in FastMCP version 0.23.0 that properly URL-encodes all path parameter values before substitution, preventing traversal sequences from being interpreted. Users should upgrade to version 0.23.0 or later to remediate this vulnerability. No additional mitigation steps are required beyond applying the official patch.

Description

FastMCP OpenAPI Provider contains a critical vulnerability in its URL construction logic that allows authenticated attackers to perform server-side request forgery (SSRF) and path traversal. The vulnerability arises because path parameters are substituted into URL templates without URL encoding, enabling attackers to inject traversal sequences like '../' to escape intended API paths. This leads to unauthorized access to internal backend endpoints with the MCP provider's authentication context.

References

Community reviews

Loading reviews…