Skip to main content
VulnerabilityPublished Updated

CVE-2026-28802: Setting `alg · none` and a blank signature appears to bypass signature verification

Affects mcp-atlassianSource GCVE Database

0
Compare

Public exploit available · CVSS 8.7 High : upgrade to 0.13.1 as a priority.

Data as of 30 Oct 2026, 08:31 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.13.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade mcp-atlassian to 0.13.1.

Affected software

ProductAffectedFixed in
Homebrewmcp-atlassianpkg:brew/mcp-atlassianOther threatsAffected
  • >=0.11.11 <0.13.1
Fixed in
  • 0.13.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Authlib to version 0.13.1 or later, where this vulnerability is fixed. Until upgraded, applications should explicitly check and disallow JWT tokens with 'alg: none' to prevent acceptance of unsigned tokens. The library does not reject 'alg: none' tokens by default in affected versions, so manual validation is necessary if patching is not immediately possible.

Description

A vulnerability in the Authlib library versions >=0.11.11 and <0.13.1 allows bypassing JWT signature verification when the token header specifies 'alg: none' with an empty signature. This flaw was introduced in versions after 1.5.2 and persists through 1.6.5, causing malicious tokens to be accepted as valid without proper signature checks. The issue can lead to authentication bypass, privilege escalation, and unauthorized access. A fix is available in version 0.13.1.

References

Community reviews

Loading reviews…