Uni-CLI: Legacy HTTP MCP transport accepted browser-originated localhost requests
Uni-CLI gives people and agents one command interface for websites, browsers, desktop applications, local tools, and MCP. Prior to version 0.225.2, Uni-CLI exposed the legacy JSON-RPC-over-HTTP MCP transport on loopback without validating browser Origin headers before routing requests. A malicious web page could send a CORS simple POST request, such as text/plain, to the local /mcp endpoint and deliver a JSON-RPC body to the dispatcher. If the user had started the local MCP HTTP transport, that page could drive tools/call requests against the user's local Uni-CLI server. The Streamable HTTP transport already enforced this browser-to-localhost boundary. The legacy stateless HTTP path did not, so the two HTTP transports had drifted. This issue is about the browser-to-localhost boundary; it does not change Uni-CLI's local-code-execution trust model. This issue has been patched in version 0.225.2.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-58497
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 06:32 UTC · Revision 1
Source evidence
Uni-CLI: Legacy HTTP MCP transport accepted browser-originated localhost requests
core-osv · Original sourcePublished 23 Oct 2026, 14:49 UTC
Uni-CLI gives people and agents one command interface for websites, browsers, desktop applications, local tools, and MCP. Prior to version 0.225.2, Uni-CLI exposed the legacy JSON-RPC-over-HTTP MCP transport on loopback without validating browser Origin headers before routing requests. A malicious web page could send a CORS simple POST request, such as text/plain, to the local /mcp endpoint and deliver a JSON-RPC body to the dispatcher. If the user had started the local MCP HTTP transport, that page could drive tools/call requests against the user's local Uni-CLI server. The Streamable HTTP transport already enforced this browser-to-localhost boundary. The legacy stateless HTTP path did not, so the two HTTP transports had drifted. This issue is about the browser-to-localhost boundary; it does not change Uni-CLI's local-code-execution trust model. This issue has been patched in version 0.225.2.
osv:CVE-2026-58497
Complete source record
{
"id": "5580b8dd3a564db01e6df0cb5b1eba68f3c22607ac01fa63ba2853a0210cd572",
"url": "https://osv.dev/vulnerability/CVE-2026-58497",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Uni-CLI: Legacy HTTP MCP transport accepted browser-originated localhost requests",
"summary": "Uni-CLI gives people and agents one command interface for websites, browsers, desktop applications, local tools, and MCP. Prior to version 0.225.2, Uni-CLI exposed the legacy JSON-RPC-over-HTTP MCP transport on loopback without validating browser Origin headers before routing requests. A malicious web page could send a CORS simple POST request, such as text/plain, to the local /mcp endpoint and deliver a JSON-RPC body to the dispatcher. If the user had started the local MCP HTTP transport, that page could drive tools/call requests against the user's local Uni-CLI server. The Streamable HTTP transport already enforced this browser-to-localhost boundary. The legacy stateless HTTP path did not, so the two HTTP transports had drifted. This issue is about the browser-to-localhost boundary; it does not change Uni-CLI's local-code-execution trust model. This issue has been patched in version 0.225.2.",
"evidence": "osv:CVE-2026-58497",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-58497",
"aliases": [
"CVE-2026-58497",
"GHSA-v3f4-w7r7-v3hm"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/olo-dot-io/uni-cli",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "69443940a3d0ec3ee2fc28a2fc782cb2069385e3"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "0.225.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "69443940a3d0ec3ee2fc28a2fc782cb2069385e3"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v0.225.2"
},
{
"range": [
{
"introduced": "0"
},
{
"fixed": "0.225.2"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"v0.225.1",
"v0.225.0",
"v0.224.1",
"v0.224.0",
"v0.223.4",
"v0.223.3",
"v0.223.2",
"v0.223.1",
"v0.223.0",
"v0.222.3",
"v0.222.2",
"v0.222.1",
"v0.222.0",
"v0.221.1",
"v0.221.0",
"v0.220.1",
"v0.220.0",
"v0.219.0",
"v0.218.1",
"v0.218.0",
"v0.217.3",
"safety/pre-v218-commit-20260504212044",
"v0.217.0",
"v0.215.0",
"v0.213.3",
"v0.213.1",
"v0.213.0",
"v0.213.0-beta.1",
"v0.212.1",
"v0.211.2",
"v0.210.0",
"v0.209.0",
"v0.208.0",
"v0.207.1",
"v0.207.0",
"v0.206.0",
"v0.205.0",
"v0.204.0",
"v0.203.0",
"v0.202.0",
"v0.201.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-58497.json"
}
}
],
"modified": "2026-10-28T02:30:26.455780791Z",
"provider": "osv",
"references": [
"https://github.com/olo-dot-io/Uni-CLI/releases/tag/v0.225.2",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/58xxx/CVE-2026-58497.json",
"https://github.com/olo-dot-io/Uni-CLI/security/advisories/GHSA-v3f4-w7r7-v3hm",
"https://nvd.nist.gov/vuln/detail/CVE-2026-58497"
],
"provider_metadata": {
"cwe_ids": [
"CWE-346",
"CWE-352"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/58xxx/CVE-2026-58497.json"
}
},
"related_cves": [
{
"value": "CVE-2026-58497",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 493078,
"published_at": "2026-10-23T14:49:42.619+00:00"
}