Skip to main content
VulnerabilityPublished

CVE-2026-123271: diillson ChatCLI · Origin Validation Error

Affects diillson ChatCLISource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to v1.215.2 when convenient.

Data as of 5 Nov 2026, 19:05 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.1
CNA (VulnCheck)CVSS 3.18.0
Patch
Available – fixed in v1.215.2, 1.215.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade ChatCLI to v1.215.2; ChatCLI to 1.215.2.

Affected software

ProductAffectedFixed in
diillsonChatCLIAffected
  • >=1.159.0 <1.215.2
Fixed in
  • v1.215.2
GoChatCLIpkg:golang/ChatCLIOther threatsAffected
  • >=1.159.0 <1.215.2
Fixed in
  • 1.215.2

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

AI-suggested

Upgrade ChatCLI to version 1.215.2 or later, where the origin validation issue in the MCP OAuth login flow is fixed. No other mitigation is necessary as the vulnerability is addressed in this official fix.

Description

ChatCLI versions before 1.215.2 have an origin validation vulnerability in the MCP OAuth login flow. The flaw involves improper validation of server-supplied Protected Resource Metadata, allowing a malicious MCP server to misuse bearer tokens by declaring unauthorized resources on the same authorization server. This can lead to token replay attacks against unintended resources.

References

Community reviews

Loading reviews…