VulnerabilityPublished 31 Oct 2026

CVE-2026-116672: Kimi cli · Authlib RFC 7592 examples omit registration-access-token client binding

Affects kimi-cliSource GCVE Database

Compare

Authoritative record:CVE-2026-116672· High 8.8

Not known to be exploited · CVSS 8.8 High.

Data as of 31 Oct 2026, 16:05 UTC

CVSS 3.1 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	8.8

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Homebrewkimi-cli`pkg:brew/kimi-cli`Other threats	Affected >=0.40	Fixed in–

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

AI-suggested

Users should avoid deploying the vulnerable example code as-is. Developers must implement the authenticate_client and check_permission methods to explicitly verify that the registration_access_token presented is bound to the client being accessed, ensuring the token's client identity matches the target client_id. Until an official fix or updated example is provided, manual code review and custom authorization checks are necessary to prevent this authorization bypass.

Description

The Kimi CLI tool's use of Authlib's RFC 7592 client configuration endpoint contains a security flaw where example code omits verifying that the registration_access_token belongs to the client being accessed. This omission allows an attacker with any valid registration_access_token and knowledge of a client_id to bypass authorization and read, update, or delete that client's registration. The vulnerability affects versions 0.40 and later. The flaw arises because the documented example implementations do not bind the token to the target client, contrary to the protocol's security model. This leads to a high-severity authorization bypass.

Impact

An attacker with any valid registration_access_token for any client and knowledge or guess of a target client_id can bypass authorization controls to read, update, or delete that client's registration data. This compromises client confidentiality, integrity, and availability within the OAuth 2.0 dynamic client registration management protocol as implemented by kimi-cli using Authlib. The flaw undermines the core security model of RFC 7592, potentially allowing unauthorized client management.

Summary

RFC 7592 defines a protocol for OAuth 2.0 dynamic client registration management, requiring that the registration_access_token presented in requests be verified to belong to the client identified in those requests. Authlib's ClientConfigurationEndpoint correctly structures the control flow but its documented example implementations for authenticate_client and check_permission omit the critical step of binding the token to the client. Specifically, authenticate_client looks up the client solely by client_id from the request payload without referencing the token, and check_permission only verifies a client property without checking the authenticated token stored in request.credential. This results in an authorization bypass where possession of any valid registration_access_token and knowledge of a client_id suffices to access or modify that client's registration. No complete, corrected example is provided in the repository. The vulnerability affects kimi-cli versions >=0.40 and has a CVSS 3.1 score of 8.8 (high severity).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Oct 2026, 16:05 UTC

Technical details

References

Community reviews

Related threats