Tracking: CVE-2026-77269
Severity: Medium
Who is affected
mcp-atlassian before 0.22.0. The report confirms reachability through registered single-file and multiple-file Confluence upload tools.
How the attack works
The upload tools do not enforce the same local-directory checks as the hardened download path. An MCP caller can select a file elsewhere on the host and have it uploaded with the server account's read permissions.
The earlier 0.17.0 download fix for CVE-2026-27825 did not cover these uploads. The report also notes a similar Jira mixin, but does not establish that it is a registered MCP tool in the configuration examined.
What to do
- Upgrade to 0.22.0 or later. An installation patched only to 0.17.0 still needs this upload fix.
- Review both single-file and batch Confluence attachments for unexpected local content.
- Limit readable mounts and revoke secrets if uploaded files contained credentials. Confirm which tools are actually exposed before assessing the Jira code path.
Scope and limits
The distinction between vulnerable code and a reachable registered tool matters when determining practical exposure.