Skip to main content
VulnerabilityPublished Updated

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

Affects fastmcpSource GCVE Database

0
Compare

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

Data as of 3 Nov 2026, 22:58 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.0
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 3 Nov 2026.

What to do

Upgrade fastmcp to 3.0.0.

Affected software

ProductAffectedFixed in
Homebrewfastmcppkg:brew/fastmcpOther threatsAffected
  • >=2.12.4_1 <3.0.0
Fixed in
  • 3.0.0

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

AI-suggested

A patch is available in Authlib version 3.0.0 that fixes this vulnerability by rejecting tokens with 'alg: none' by default. Users should upgrade to version 3.0.0 or later. Until upgrading, applications must implement explicit checks to disallow 'alg: none' tokens to prevent acceptance of forged JWTs. The vendor does not indicate any automatic mitigation or that no action is required.

Description

A vulnerability in the Authlib library versions >=2.12.4_1 and <3.0.0 allows JWT tokens with the header 'alg: none' and an empty signature to bypass signature verification. This issue was introduced in version 1.6.0 and persists through 1.6.5. Applications using affected versions may accept forged JWTs without proper verification, leading to authentication bypass and privilege escalation. The vulnerability is fixed in version 3.0.0.

References

Community reviews

Loading reviews…