What is the CVSS score of CVE-2025-57282?

CVE-2025-57282 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of ngrok (npm) are affected by CVE-2025-57282?

The ngrok npm package (versions 4.3.3 and 5.0.0-beta.2) contains a command injection vulnerability (CVSS 8.8) enabling unauthenticated remote code execution with complete system access.

How to fix or mitigate CVE-2025-57282?

Within 24 hours: Execute 'npm list ngrok' across all development and production environments to identify affected instances; immediately quarantine systems running versions 4.3.3 or 5.0.0-beta.2 from sensitive networks. Within 7 days: Downgrade all ngrok instances to stable versions prior to 4.3.3 (e.g., 4.3.2 or earlier); implement input validation to sanitize all data passed to ngrok parameters; deploy network segmentation to restrict ngrok-dependent services from sensitive assets; enable comprehensive logging of ngrok process execution and shell commands. Within 30 days: Monitor vendor advisories daily for patch availability and immediately test any released patch in staging before production deployment; evaluate alternative tunneling solutions (Cloudflare Tunnel, AWS Systems Manager Session Manager) to reduce ngrok dependency; conduct application code review to eliminate unnecessary shell-level command invocations.

ngrok (npm) CVE-2025-57282

EUVD-2025-209888 HIGH

Command Injection (CWE-77)

2026-05-18 mitre

GHSA-qr28-p3wr-mxq3

Command Injection N A

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

8.1 HIGH

Command execution gives full C/I/A impact, but as a library flaw exploitation depends on the host app routing untrusted input into the vulnerable option, so AC:H.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 23, 2026 - 18:07 vuln.today

CVE Published

May 18, 2026 - 00:00 cve.org

HIGH 8.8

CVE Published

May 18, 2026 - 00:00 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

ngrok v4.3.3 and 5.0.0-beta.2 is vulnerable to Command Injection.

AnalysisAI

Command injection in the ngrok Node.js package (npm) versions 4.3.3 and 5.0.0-beta.2 allows attackers to execute arbitrary OS commands on the host running the tunneling wrapper, achieving total loss of confidentiality, integrity, and availability (CVSS 8.8). The flaw stems from unsanitized input being passed to a shell when invoking the underlying ngrok binary. There is no public exploit identified as weaponized, though a reference gist appears to contain proof-of-concept material, and EPSS remains low at 0.21% with SSVC marking exploitation status as 'none'.

Technical ContextAI

The affected component is the popular 'ngrok' npm module - a Node.js wrapper that programmatically manages ngrok tunnels by shelling out to the native ngrok agent binary. CWE-77 (Improper Neutralization of Special Elements used in a Command) indicates that connection or configuration parameters (e.g., tunnel options, region, auth token, or binary path passed to the API) are concatenated into a shell command without sanitization, so shell metacharacters (;, |, `, $()) supplied through those parameters are interpreted by the operating system rather than treated as literal data. The CPE data is a placeholder ('cpe:2.3:a:n/a:n/a') and provides no additional product identification; the npmjs.com reference is the authoritative anchor confirming this is the JavaScript package rather than the standalone ngrok agent itself.

RemediationAI

No vendor-released fixed version is identified in the provided data at time of analysis, so the primary action is to review the npm advisory and package release notes on https://www.npmjs.com for the ngrok package and upgrade to a patched release once published; do not rely on the 5.0.0-beta.2 pre-release. As compensating controls until a fix is confirmed, never pass user- or attacker-controlled input into ngrok API options (tunnel names, region, addr, binary path, or auth strings) - hardcode or strictly allowlist these values, which removes the injection vector at the cost of losing dynamic per-request tunnel configuration. If dynamic values are unavoidable, validate them against a strict character allowlist (e.g., alphanumerics only) to reject shell metacharacters, and run the Node process under a low-privilege, sandboxed account to limit the blast radius of any successful injection. Consult the VulDB advisory (https://vuldb.com/vuln/364483) and NVD entry for updates.