Skip to main content
VulnerabilityPublished

CVE-2026-77242: sooperset mcp-atlassian · Time-of-check Time-of-use (TOCTOU) Race Condition

Affects sooperset mcp-atlassianSource CVE Database V5

0
Compare

Mentioned vulnerabilities

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

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 22% 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:N/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 6 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 sooperset mcp-atlassian to version 0.22.0 or later, where this TOCTOU race condition vulnerability is fixed. No other mitigations are indicated or required according to the advisory.

Description

CVE-2026-77242 is a time-of-check to time-of-use (TOCTOU) race condition vulnerability in sooperset's mcp-atlassian server prior to version 0.22.0. The flaw arises because the hostname validation function validate_url_for_ssrf resolves DNS addresses separately from the actual connection attempt, allowing an attacker to exploit short-lived DNS responses to bypass SSRF protections. This can lead to unauthorized access to internal or metadata endpoints. The issue is fixed in version 0.22.0.

References

Community reviews

Loading reviews…