CVE-2026-124503 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
The mcp-atlassian MCP server fails to properly validate file paths in validate_safe_path, allowing a crafted path argument to traverse directories. An attacker who can send requests to the server may read or write files outside the intended location.
first public Nov 8, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running mcp-atlassian up to 0.24.0 as an MCP server that accepts file path arguments from clients or model output. Deployments that do not expose file path tools to untrusted input are less exposed. The sources do not describe the exact exploitation conditions.
Not affected if no-file-path-tools, version-0.24.1-or-later
Who cares atlassian, mcp, python
pip show mcp-atlassian and compare it to 0.24.0validate_safe_path in src/mcp_atlassian/utils/io.py to confirm the affected code is present0.24.1A 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.
This page as .md · .json · 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.