Critical (CVSS 10.0, GitHub Advisory Database)Path traversal

CVE-2026-77244 / CVE-2026-77258: mcp-atlassian HTTP authentication bypass and arbitrary file read (< 0.22.0)

Product
mcp-atlassian (PyPI)
CVE
CVE-2026-77244, CVE-2026-77258
Affected
< 0.22.0
Fixed in
0.22.0

Last verified against sources: October 16, 2026

Am I affected?

mcp-atlassian (PyPI): affected < 0.22.0. Fixed in 0.22.0.

What to do now

  1. Upgrade mcp-atlassian to 0.22.0 or later. [1][2]

General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.

What happened

  • According to GitHub Advisory Database's advisory (Sept 22, 2026), AtlassianOpaqueTokenVerifier.verify_token() in mcp-atlassian accepted any non-empty string as a valid token in HTTP transport deployments (CVE-2026-77244). [1]
  • Separately, upload_attachment read and uploaded local files to Confluence without calling validate_safe_path() (CVE-2026-77258). [2]

Impact

  • Unauthenticated callers could access HTTP deployments using server-side credentials, and an agent or attacker could read arbitrary host files and exfiltrate them as Confluence attachments. [1][2]

What was done

  • Patched in mcp-atlassian 0.22.0. [1][2]

Sources

  1. GHSA-wrhw-j3f9-8vc6 (CVE-2026-77244) — GitHub Advisory Database
  2. GHSA-93xw-j965-9mx3 (CVE-2026-77258) — GitHub Advisory Database

Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.

Share advisory brief with your team

Copy a plain-text summary for Slack, GitHub issues, or team security channels.

Brief
[CVE-2026-77244, CVE-2026-77258] CVE-2026-77244 / CVE-2026-77258: mcp-atlassian HTTP authentication bypass and arbitrary file read (< 0.22.0)
Product: mcp-atlassian (PyPI) | Affected: < 0.22.0 | Fixed in: 0.22.0
Summary: According to GitHub Advisory Database's advisory (Sept 22, 2026), AtlassianOpaqueTokenVerifier.verify_token() in mcp-atlassian accepted any non-empty string as a valid token in HTTP transport deployments (CVE-2026-77244).
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/09/cve-2026-77244-77258-mcp-atlassian-auth-file-read
Was this page useful?

Corrections

Report an error or request a correction. We review requests within 5 business days and add a dated correction note.

10 to 2,000 characters. A link to a source helps. Stored as plain text.

Discussions for CVE-2026-77244, CVE-2026-77258

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Check before you install

Paste a package name or a GitHub link and get a clear answer in seconds: Block, Review or No known issues. No account needed.

Check a package

Questions? Contact us