Skip to main content
VulnerabilityPublished

CVE-2026-124503: sooperset mcp-atlassian · Path Traversal

Affects sooperset mcp-atlassianSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium · fixed in 0.24.1 : patch sooperset mcp-atlassian as a priority.

Data as of 10 Nov 2026, 10:06 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.05.3
CNA (VulDB)CVSS 3.14.3
CNA (VulDB)CVSS 3.04.3
CNA (VulDB)CVSS 2.04.0
Patch
Available – fixed in 0.24.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
soopersetmcp-atlassianAffected
  • 0.1 – 0.24.0
24 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:sooperset:mcp-atlassian:*:*:*:*:*:*:*:*

AI-suggested

Upgrade sooperset mcp-atlassian to version 0.24.1 or later, which contains the fix for this path traversal vulnerability. No other mitigations are specified or required beyond applying this official update.

Description

CVE-2026-124503 is a path traversal vulnerability in sooperset mcp-atlassian affecting versions up to 0.24.0. The flaw exists in the validate_safe_path function in src/mcp_atlassian/utils/io.py, allowing remote attackers to manipulate the path argument to traverse directories. A public exploit is available. Upgrading to version 0.24.1 addresses the issue.

References

Community reviews

Loading reviews…