Is CVE-2026-73496 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-73496 being exploited in the wild.

How severe is CVE-2026-73496?

High severity, with a CVSS score of 7.7, published 14 September 2026.

Which products and versions are affected?

mcp-atlassian (PyPI) ECOSYSTEM:introduced=0,fixed=0.22.0.

Is there a fix for CVE-2026-73496?

Yes. mcp-atlassian (PyPI): upgrade to 0.22.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-73496 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-73496?

Check whether you run mcp-atlassian (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-73496: MCP Atlassian path traversal in attachment upload

CVE-2026-73496 · Severity: high · CVSS 7.7 · Published 2026-09-14

MCP Atlassian is a server that integrates AI assistants with Atlassian collaboration tools like Jira and Confluence. In multi-user or remote deployments, attackers with write access to the attachment tools could upload files from arbitrary locations on the server (using absolute paths or directory traversal sequences), potentially exposing sensitive files, credentials stored in environment variables, or data from other tenants. Single-user local deployments are not affected due to trust boundaries.

Technologies: mcp-atlassian (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-73496 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-73496 being exploited in the wild.
How severe is CVE-2026-73496?: High severity, with a CVSS score of 7.7, published 14 September 2026.
Which products and versions are affected?: mcp-atlassian (PyPI) ECOSYSTEM:introduced=0,fixed=0.22.0.
Is there a fix for CVE-2026-73496?: Yes. mcp-atlassian (PyPI): upgrade to 0.22.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73496 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-73496?: Check whether you run mcp-atlassian (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

mcp-atlassian (PyPI): upgrade to 0.22.0 or later
```
pip install "mcp-atlassian>=0.22.0"
```

Technical details

A path traversal vulnerability exists in the `confluence_upload_attachment`, `confluence_upload_attachments`, and `jira_update_issue` tools (via the `attachments` parameter). Client-supplied file paths are passed directly to `upload_attachment` functions in `src/mcp_atlassian/confluence/attachments.py` and `src/mcp_atlassian/jira/attachments.py` without validation against the server's workspace directory. An attacker with write-tool access in HTTP, SSE, or multi-user deployments can provide absolute paths or traversal sequences (e.g., `../../../etc/passwd`) to read and exfiltrate arbitrary server files, including credentials and tenant data. The fix, deployed in version 0.22.0, introduces a `validate_safe_path` function that confines all file paths to the server's working directory before opening files.

Affected products

MCP Atlassian MCP Atlassian prior to 0.22.0

Identifiers

CVE-2026-73496
GHSA-wm45-qh3g-v83f

Timeline

2026-09-14: disclosed
2026-07-10: patched: Fix merged in version 0.22.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.