How severe is GHSA-6xpm-ggf7-wc3p?

GHSA-6xpm-ggf7-wc3p has a CVSS score of 9.6/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6xpm-ggf7-wc3p?

GHSA-6xpm-ggf7-wc3p affects the following packages: mcp-remote (npm). Ecosystems affected: npm.

How do I fix GHSA-6xpm-ggf7-wc3p?

Update mcp-remote to 0.1.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6xpm-ggf7-wc3p is resolved across your whole dependency graph.

How do I detect GHSA-6xpm-ggf7-wc3p in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mcp-remote. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6xpm-ggf7-wc3p if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6xpm-ggf7-wc3p?

O3 pinpoints whether GHSA-6xpm-ggf7-wc3p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6xpm-ggf7-wc3p actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-6xpm-ggf7-wc3p, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-6xpm-ggf7-wc3p?

GHSA-6xpm-ggf7-wc3p has an EPSS (Exploit Prediction Scoring System) score of 76.6%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-6xpm-ggf7-wc3p?

GHSA-6xpm-ggf7-wc3p is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-6xpm-ggf7-wc3p published, and has it been updated?

GHSA-6xpm-ggf7-wc3p was published on July 9, 2025 and was last updated on July 9, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-6xpm-ggf7-wc3p

CRITICAL

mcp-remote exposed to OS command injection via untrusted MCP server connections

Also known asCVE-2025-6514

Published

Jul 9, 2025

Updated

Jul 9, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

76.6%probability of exploitation in next 30 days

Very High Risk99th percentile+64.46%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

mcp-remotenpm

378Kdownloads / week

Description

mcp-remote is exposed to OS command injection when connecting to untrusted MCP servers due to crafted input from the authorization_endpoint response URL

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mcp-remote`	≥ 0.0.5&&< 0.1.16	0.1.16

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Cyberency/CVE-2025-6514

mcp-remote exposed to OS command injection

⭐ 7🍴 1Nov 2025

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mcp-remote. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mcp-remote to 0.1.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6xpm-ggf7-wc3p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6xpm-ggf7-wc3p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6xpm-ggf7-wc3p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

mcp-remote is exposed to OS command injection when connecting to untrusted MCP servers due to crafted input from the authorization_endpoint response URL

O3 Security · Impact-Aware SCA

Is GHSA-6xpm-ggf7-wc3p in your dependencies?

O3 detects GHSA-6xpm-ggf7-wc3p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works