Skip to main content
VulnerabilityPublished

CVE-2026-77261: sooperset mcp-atlassian · Server-Side Request Forgery (SSRF)

Affects sooperset mcp-atlassianSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 0.22.0 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.22.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 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 5 Nov 2026.

What to do

Upgrade mcp-atlassian and sooperset/mcp-atlassian to 0.22.0.

Affected software

ProductAffectedFixed in
soopersetmcp-atlassianAffected
  • <0.22.0
Fixed in
  • 0.22.0
GitHubsooperset/mcp-atlassianpkg:github/sooperset/mcp-atlassianOther threatsAffected
  • <0.22.0
Fixed in
  • 0.22.0

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

AI-suggested

Upgrade MCP Atlassian to version 0.22.0 or later, where the _make_ssrf_safe_hook is properly included to prevent SSRF via redirect validation. No other mitigation is indicated by the vendor advisory. Patch status is confirmed as fixed in 0.22.0.

Description

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, _make_ssrf_safe_hook is omitted from JiraFetcher and ConfluenceFetcher sessions created through the basic-auth and oauth_pat branches. If an attacker-controlled or compromised configured Atlassian instance returns a redirect to an internal address, those sessions can follow the redirect without revalidating its destination. This issue is fixed in version 0.22.0.

References

Community reviews

Loading reviews…