{"answers":{"affected":"3 open source packages ship an affected version, including mcp-atlassian.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73498 exists.","fix":"Upgrade mcp-atlassian to 0.22.0 or later.","what":"CVE-2026-73498 is a high-severity path traversal vulnerability in sooperset mcp-atlassian, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73498 and fix it if it is affected.\n\nWhat it is: CVE-2026-73498 is a high-severity path traversal vulnerability in sooperset mcp-atlassian, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73498 exists.\n\nAffected packages and fixed versions:\n- mcp-atlassian (PyPI): affected all versions; fixed in 0.22.0\n- mcp-atlassian (PyPI): affected all versions; fixed in 0.22.0\n- mcp-atlassian (PyPI): affected all versions; fixed in 0.22.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73498/ (Markdown: https://insights.sbomify.com/CVE-2026-73498/index.md)","id":"CVE-2026-73498","markdown":"https://insights.sbomify.com/CVE-2026-73498/index.md","name":"CVE-2026-73498","record":{"aliases":["GHSA-g5r6-gv6m-f5jv","PYSEC-2026-3683"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP Atlassian server","requires_auth":"low_privilege","summary":"An authenticated MCP client can read arbitrary server files and exfiltrate them as Confluence attachments due to missing path validation.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, confluence_upload_attachment passes its client-supplied file_path directly to open(file_path, \"rb\") in src/mcp_atlassian/confluence/attachments.py through _upload_attachment_direct() without calling validate_safe_path. An authenticated MCP client can read any file accessible to the server process and exfiltrate it to Confluence as an attachment. If an AI agent can be induced to call the tool through untrusted content, the same flaw can disclose server environment variables such as CONFLUENCE_API_TOKEN and other credentials. This issue is fixed in version 0.22.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"mcp-atlassian: Arbitrary file read via missing path validation in confluence_upload_attachment","id":"CVE-2026-73498","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"etcd: Watch API authorization bypass via open-ended range requests","id":"CVE-2026-73499"},"packages":[{"ecosystem":"PyPI","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"mcp-atlassian","purl":null,"source":"GHSA-g5r6-gv6m-f5jv"},{"ecosystem":"PyPI","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"mcp-atlassian","purl":"pkg:pypi/mcp-atlassian","source":"GHSA-g5r6-gv6m-f5jv"},{"ecosystem":"PyPI","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"mcp-atlassian","purl":"pkg:pypi/mcp-atlassian","source":"PYSEC-2026-3683"}],"prev":{"headline":"MCP Atlassian: DNS-rebinding TOCTOU bypass of the SSRF fix (CVE-2026-27826)","id":"CVE-2026-73497"},"products":["mcp-atlassian"],"published":"2026-08-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["sooperset"]},"summary":"An authenticated MCP client can read arbitrary server files and exfiltrate them as Confluence attachments due to missing path validation.","url":"https://insights.sbomify.com/CVE-2026-73498/"}