# CVE-2026-124503: sooperset mcp-atlassian io.py validate_safe_path path traversal


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-8fch-hp3f-8mp8, GHSA-qh7q-jmc7-rc7j

## What is CVE-2026-124503?

CVE-2026-124503 is a medium-severity vulnerability in sooperset mcp-atlassian, published on 10 Nov 2026. 

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-124503?


## How do I fix CVE-2026-124503?

No fix has been published for CVE-2026-124503 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124503 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124503 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124503 and fix it if it is affected.

What it is: CVE-2026-124503 is a medium-severity vulnerability in sooperset mcp-atlassian, published on 10 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124503 exists.

Affected product: sooperset mcp-atlassian. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124503/ (Markdown: https://insights.sbomify.com/CVE-2026-124503/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124503
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124503
- OSV: https://osv.dev/vulnerability/CVE-2026-124503

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124503/
Summaries are generated and may contain mistakes; the official description above is the record.