CVE-2026-28802: Setting `alg · none` and a blank signature appears to bypass signature verification
Affects kimi-cliSource GCVE Database
Not known to be exploited : upgrade to 1.11.0 when convenient.
Data as of 26 Oct 2026, 08:30 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.11.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:PExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade kimi-cli to 1.11.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu:25.10python-authlibpkg:deb/ubuntu/python-authlib?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Homebrewkimi-clipkg:brew/kimi-cliOther threats | Affected
| Fixed in
|
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 for this vulnerability. Users should upgrade to a fixed version of the kimi-cli Authlib library to ensure proper JWT signature verification. Check the vendor advisory or official release notes for the exact patched versions and apply updates accordingly.
Description
A vulnerability in the kimi-cli's Authlib library versions 1.5.1-1, 1.5.2-1, 1.6.0-1, and versions from 1.6.5 up to but not including 1.6.7 allows bypassing JWT signature verification when the token uses the 'alg: none' algorithm with an empty signature. This flaw enables acceptance of forged JWTs without proper signature validation, potentially leading to authentication bypass and unauthorized access. The issue was introduced in the upgrade from version 1.5.2 to 1.6.0 and persists in later affected versions. A patch is available to address this vulnerability.
References
- ubuntu.com/security/CVE-2026-28802 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-28802 (opens in a new tab)
- github.com/authlib/authlib/commit/a61c2acb807496e67f32051b5f1b1d5ccf8f0a75 (opens in a new tab)
- github.com/authlib/authlib/commit/b87c32ed07b8ae7f805873e1c9cafd1016761df7 (opens in a new tab)
- github.com/authlib/authlib/security/advisories/GHSA-7wc2-qxgw-g8gg (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-28802 (opens in a new tab)
- github.com/authlib/authlib (opens in a new tab)