Vulnerabilities in pkg:npm/@zenalexa/unicli

PACKAGE
Share
Advisory Summary

GHSA-v3f4-w7r7-v3hm is a HIGH legacy http mcp transport accepted vulnerability (CWE-346: Origin Validation Error) affecting Uni-CLI libraries in the npm ecosystem. The issue involves legacy http mcp transport accepted browser-originated localhost requests. Remediation is available by upgrading affected packages to version 0.225.2.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@zenalexa/unicli

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@zenalexa/unicli. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-v3f4-w7r7-v3hm - HIGH Uni-CLI: Legacy HTTP MCP transport accepted browser-originated localhost requests

GHSA-v3f4-w7r7-v3hm at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-v3f4-w7r7-v3hm
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-346: Origin Validation Error
Affected Product Uni-CLI
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-v3f4-w7r7-v3hm

To remediate this vulnerability, upgrade all affected Uni-CLI dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@zenalexa/unicli fixed: 0.225.2 
npm install @zenalexa/unicli@0.225.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @zenalexa/unicli

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-v3f4-w7r7-v3hm, inspect your project dependencies using npm:

npm ls @zenalexa/unicli

Analyze the terminal output to locate any version of Uni-CLI in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.225.2), your application is affected.

Note: The npm ls @zenalexa/unicli command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-346: Origin Validation Error, where the product does not properly verify that the source of data or communication is valid. In Uni-CLI, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact Uni-CLI versions before 0.225.2 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. ## Patches Version 0.225.2 fixes the issue by moving the Origin policy into a shared guard and applying it before routing in both HTTP transports. Non-loopback browser Origins are rejected with HTTP 403 before health, OAuth, or /mcp dispatch runs. Non-browser clients that omit Origin remain supported. ## Workarounds Upgrade to 0.225.2 or later. If upgrading is not immediately possible, do not expose the legacy HTTP MCP transport to browser-originated traffic; use the default stdio transport or the Streamable HTTP transport instead. ## Credits Reported privately by Ryan Vonbrubeck ([@dodge1218](https://github.com/dodge1218)).

GHSA-v3f4-w7r7-v3hm Affected Uni-CLI Versions

1 component(s)
Fixed Versions:
0.225.2
Product / Package Ecosystem Affected Versions Fixed Version
@zenalexa/unicli
npm/@zenalexa/unicli
npm
< 0.225.2
0.225.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/olo-dot-io/Uni-CLI/security/advisories/GHSA-v3f4-w7r7-v3hm
Uni-CLI Source Repository REPOSITORY
https://github.com/olo-dot-io/Uni-CLI

Frequently Asked Questions

What is GHSA-v3f4-w7r7-v3hm?
GHSA-v3f4-w7r7-v3hm is a security vulnerability in Uni-CLI involving Legacy HTTP MCP transport accepted browser-originated localhost requests under CWE-346: Origin Validation Error.
Which Uni-CLI versions are affected?
Affected versions include releases prior to 0.225.2 across affected packages: @zenalexa/unicli.
What version fixes GHSA-v3f4-w7r7-v3hm?
Upgrading to 0.225.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @zenalexa/unicli affected?
Yes, @zenalexa/unicli is affected in releases prior to 0.225.2. Upgrade your dependency to 0.225.2 or later.
What CWE is associated with GHSA-v3f4-w7r7-v3hm?
GHSA-v3f4-w7r7-v3hm is classified under CWE-346: Origin Validation Error (The product does not properly verify that the source of data or communication is valid.).
How can I check npm dependencies for GHSA-v3f4-w7r7-v3hm?
Run the dependency tree command: 'npm ls @zenalexa/unicli'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v3f4-w7r7-v3hm",
  "modified" : "2026-06-19T21:43:09Z",
  "published" : "2026-06-19T21:43:09Z",
  "aliases" : [ ],
  "summary" : "Uni-CLI: Legacy HTTP MCP transport accepted browser-originated localhost requests",
  "details" : "## Impact\n\nUni-CLI versions before 0.225.2 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.\n\nThe 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.\n\n## Patches\n\nVersion 0.225.2 fixes the issue by moving the Origin policy into a shared guard and applying it before routing in both HTTP transports. Non-loopback browser Origins are rejected with HTTP 403 before health, OAuth, or /mcp dispatch runs. Non-browser clients that omit Origin remain supported.\n\n## Workarounds\n\nUpgrade to 0.225.2 or later. If upgrading is not immediately possible, do not expose the legacy HTTP MCP transport to browser-originated traffic; use the default stdio transport or the Streamable HTTP transport instead.\n\n## Credits\n\nReported privately by Ryan Vonbrubeck ([@dodge1218](https://github.com/dodge1218)).",
  "severity" : [ {
    "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" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@zenalexa/unicli"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.225.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/olo-dot-io/Uni-CLI/security/advisories/GHSA-v3f4-w7r7-v3hm"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/olo-dot-io/Uni-CLI"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-346", "CWE-352" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T21:43:09Z",
    "nvd_published_at" : null
  }
}