cve.bz

CVE-2026-124503

2.1 lowEPSS 0.5%

Low (2.1) in sooperset mcp-atlassian. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability was identified in sooperset mcp-atlassian up to 0.24.0. This issue affects the function validate_safe_path of the file src/mcp_atlassian/utils/io.py. The manipulation of the argument path leads to path traversal. The attack may be initiated remotely. The exploit is publicly available and might be used. Upgrading to version 0.24.1 is capable of addressing this issue. Upgrading the affected component is recommended. This CVE was requested by the vendor.

Severity

CVSS 4.0

2.1 low
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

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.5% estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
VulDB (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-124503 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-124503?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-124503?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-124503 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
sooperset mcp-atlassian0.1
sooperset mcp-atlassian0.2
sooperset mcp-atlassian0.3
sooperset mcp-atlassian0.4
sooperset mcp-atlassian0.5
sooperset mcp-atlassian0.6
sooperset mcp-atlassian0.7
sooperset mcp-atlassian0.8
sooperset mcp-atlassian0.9
sooperset mcp-atlassian0.10
sooperset mcp-atlassian0.11
sooperset mcp-atlassian0.12
sooperset mcp-atlassian0.13
sooperset mcp-atlassian0.14
sooperset mcp-atlassian0.15
sooperset mcp-atlassian0.16
sooperset mcp-atlassian0.17
sooperset mcp-atlassian0.18
sooperset mcp-atlassian0.19
sooperset mcp-atlassian0.20
sooperset mcp-atlassian0.21
sooperset mcp-atlassian0.22
sooperset mcp-atlassian0.23
sooperset mcp-atlassian0.24.0

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. Score 5.3 → 2.1 low
  2. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON