[mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty token (CVE-2026-77244) | HOL Guard CVE

Critical · CVSS 10.0CVE-2026-77244

[mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty token

Answer in brief

CVE-2026-77244 records a Critical severity (CVSS 10.0) vulnerability in [mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty token. The current sources do not mark it as known exploited. The current feed maps sooperset/mcp-atlassian (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 22, 2026Updated Sep 22, 2026Source checked Sep 22, 2026First seen by HOL Sep 22, 2026Material review Sep 22, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 10.0
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 10.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps sooperset/mcp-atlassian (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
sooperset/mcp-atlassiangeneric	<0.22.0	0.22.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for sooperset/mcp-atlassian.
Review the reported fix. Update sooperset/mcp-atlassian to 0.22.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 22, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.