AAK-MCP-UNICLI-CVE-2026-58497-001: Uni-CLI from 0.208.0 below 0.225.2: the legacy HTTP MCP transport answers a web page's request to loopback /mcp
- Severity
- HIGH
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
UniCliLegacyHttpTransportOrigin
What it detects
Uni-CLI (@zenalexa/unicli on npm; olo-dot-io/Uni-CLI) gives people and agents one command interface for websites, browsers, desktop applications, local tools and MCP, and can serve MCP over HTTP on loopback. Before 0.225.2 its legacy JSON-RPC-over-HTTP transport routed requests without checking the browser's Origin, so a web page could send a CORS-simple POST (text/plain) to the local /mcp endpoint and drive tools/call against the user's Uni-CLI server once that transport was started (CVE-2026-58497, CVSS 4.0 8.6, CWE-346/CWE-352, GHSA-v3f4-w7r7-v3hm). The Streamable HTTP transport already enforced that browser-to-localhost boundary; the legacy path had drifted from it. 0.225.2 routes every request on both transports through one isOriginAllowed guard. The flaw is the browser-to-localhost boundary, not Uni-CLI's local-code-execution trust model.
How to fix
Upgrade @zenalexa/unicli to 0.225.2 or later and pin it. Until then serve MCP over stdio, or over the Streamable HTTP transport, which checked Origin before 0.225.2 too.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-UNICLI-CVE-2026-58497-001
Limitations
Reports @zenalexa/unicli from 0.208.0 below 0.225.2 where a package.json, lockfile or MCP config states the version, reporting a range that admits an affected version. 0.207.1, the first release, has no HTTP transport and is not reported. latest was 1.3.0 on 2026-10-24 and states no version, so an unversioned reference is not reported. It reads the version, not which transport runs, so a server only ever started over stdio is reported too. npm's uni-cli is another project and is not matched. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-58497
- OWASP MCP Top 10: MCP07:2025 (Insufficient Authentication & Authorization), MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
- OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-SUPPLY-08 (MCP-Specific Vuln)
- CSA AI Controls Matrix (AICM): IVS-04, STA-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-UNICLI-CVE-2026-58497-001.md: the page then shows that text, with the registry reference appended under it.