CVE-2026-124503
Deferred Deferred - Pending Action

Path Traversal in sooperset mcp-atlassian

Publication date: 2026-11-10

Last updated on: 2026-11-10

Assigner: VulDB

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-10
Last Modified
2026-11-10
Generated
2026-11-10
AI Q&A
2026-11-10
EPSS Evaluated
N/A
NVD
CVE-2026-124503
EUVD
EUVD-2026-120865

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
sooperset mcp-atlassian to 0.24.0 (inc)
sooperset mcp-atlassian 0.24.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a path traversal flaw in the mcp-atlassian tool up to version 0.24.0. It exists in the validate_safe_path function in src/mcp_atlassian/utils/io.py. The issue allows authenticated remote attackers to read arbitrary files on the server by exploiting improper path validation during file uploads. The function incorrectly uses the server's current working directory as a boundary instead of a restricted directory, enabling access to sensitive files like /etc/passwd or .env files.

Detection Guidance

Check if the installed version of mcp-atlassian is prior to 0.24.1 by running: pip show mcp-atlassian or grep version in your deployment files. Review server logs for unusual file access patterns or exfiltration attempts during upload operations. Inspect the working directory configuration in systemd units or shell launch scripts to ensure it is not set to filesystem root.

Impact Analysis

If you use mcp-atlassian in a multi-user HTTP/SSE deployment with a wide current working directory, attackers could read sensitive files on your server. This includes configuration files, credentials, or system files. The attack is stealthy as it uses legitimate upload mechanisms. Containerized deployments using the official image are not affected.

Mitigation Strategies
  • Upgrade mcp-atlassian to version 0.24.1 or later immediately.
  • Configure a dedicated upload directory by setting MCP_ATLASSIAN_UPLOAD_DIR to a restricted path.
  • Ensure the working directory is not set to filesystem root in systemd units or shell scripts.
  • Restrict file paths for tools to an explicit directory as per the upgrade notes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-124503. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...