VulnSocial

CVE-2026-77244Patch(mcp-atlassian / mcp_atlassian)

LOWCVSS 10.0 · CRITICAL

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch mcp-atlassian mcp_atlassian systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, the HTTP transport accepts requests without a verified user identity and downstream fetcher construction falls back to the operator's globally configured Jira or Confluence credentials. A network client that can reach the MCP endpoint can invoke Atlassian tools as the operator, including read and write operations available to that account. The advisory traces the vulnerable input and processing flow through UserTokenMiddleware, AtlassianOpaqueTokenVerifier, _get_fetcher, and streamable-http, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.

mcp-atlassian CVEsBack to dashboard
0.5/ 10 priority

Sources & remediation

Patch / fix
Exploit / PoC references
Other references
Weakness type (CWE)
CWE-287CWE-303CWE-862

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • mcp_atlassian

Threat summary

  • Patch or workaround signal is available
  • 4 mentions across 4 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 3 signals
  • Technical details provided in 4 signals
  • Disclosure: 1 classified signal
  • Peaked 3d ago at 1 mentions (2026-09-22); latest day: 1
  • 4 total mentions across 4 days

Affected systems

Vendors
mcp-atlassian
Products
mcp_atlassian

Deep dive

Activity timeline4 mentions / 4d
00111Mentions · 2026-09-22: 1Mentions · 2026-09-23: 1Mentions · 2026-10-03: 1Mentions · 2026-10-22: 1Patch / Workaround · 2026-09-22: 1Patch / Workaround · 2026-10-03: 1Patch / Workaround · 2026-10-22: 1Technical Details · 2026-09-22: 1Technical Details · 2026-09-23: 1Technical Details · 2026-10-03: 1Technical Details · 2026-10-22: 109-2209-2310-0310-22
Signal classification2 categories
Patch
375.0%
Disclosure
125.0%
Referenced assets2 URLs
Classification over time
DateTotalLabels
2026-09-221
Patch1
2026-09-231
Disclosure1
2026-10-031
Patch1
2026-10-221
Patch1
Full discourse4 posts
  • ATIK@atikbytes
    Patch

    1/ Running mcp-atlassian or the GitLab MCP server over HTTP? Two critical bugs mean anyone who can reach the port can act as you. Quick rundown 🧵 2/ mcp-atlassian before 0.22.0 (CVE-2026-77244, CVSS 10): the HTTP transport accepts any non-empty token, then falls back to the operator's Jira/Confluence credentials. Upgrade to 0.22.0, or stay on stdio until you can. https://vibevulns.com/issues/cve-2026-77244-mcp-atlassian-http-transport-auth-bypass/

    Post summary

    The text announces CVE-2026-77244 in mcp-atlassian's HTTP transport (CVSS 10), detailing the auth-bypass mechanism and explicitly recommending an upgrade to version 0.22.0 as the primary remediation.

    1001056
    843 followersView on X
  • Upwind Security MDR@UpwindMDR
    Patch

    🚨Critical - MCP Atlassian HTTP Transport Auth Bypass (CVE-2026-77244) mcp-atlassian’s HTTP transport prior to 0.22.0 accepts requests without a verified user identity; fetcher construction can fall back to the operator’s globally configured Jira/Confluence credentials. Any network client with endpoint access can invoke Confluence/Jira tools as the operator for read/write actions. 👉Affected: mcp-atlassian < 0.22.0 | Upgrade to 0.22.0

    Post summary

    The text announces CVE-2026-77244, an authentication bypass in mcp-atlassian HTTP transport prior to 0.22.0 allowing unauthenticated clients to invoke Jira/Confluence tools with operator credentials, and directs users to upgrade to version 0.22.0 as remediation.

    1001081
    310 followersView on X
  • Sagar Tanur 🇮🇳@Sagarvd01
    Patch

    mcp-atlassian CVE-2026-77244 (CVSS 10.0, NVD ~Sep 22, fresh writeups Oct 2): HTTP transport ran with the operator's Jira/Confluence token when Authorization was missing or literally Bearer anything. token verifier accepted any non-empty string. UserTokenMiddleware let missing headers through. fetchers fell back to env credentials. one unauthenticated tools/call to /mcp was enough. fix landed in 0.22.0 (Jul 10); SSE path needed 0.23.1 (Aug 19). GHSA-wrhw-j3f9-8vc6. my take: a single-user "quickstart" credential behind an open HTTP port is not a personal tool. it is a shared operator identity. upgrade, leave ALLOW_GLOBAL_CRED_FALLBACK off, bind localhost, rotate the token if that port was ever reachable.

    Post summary

    The text details a critical authentication bypass in mcp-atlassian (CVE-2026-77244) where unauthenticated requests could leverage operator credentials via fallback mechanisms, and explicitly identifies the patched versions (0.22.0/0.23.1) along with required configuration hardening steps.

    0010090
    195 followersView on X
  • Severity Daily@severitydaily
    Disclosure

    mcp-atlassian's token verifier accepted any non-empty string, and sending no Authorization header at all worked too, falling back to the operator's Jira token. CVSS 10.0. No exploitation reported. https://severitydaily.com/mcp-atlassian-cve-2026-77244-token-verifier-any-non-empty-string-74-days/

    Post summary

    The tweet announces a critical CVE (CVSS 10.0) where the token verifier accepts any non‑empty string and lacks proper Authorization checks, with no reported exploitation or remediation details.

    0010060
    27 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appmcp-atlassianmcp_atlassian---

Explore more

Back to dashboardmcp-atlassian CVEsmcp_atlassian vulnerabilities