dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-57282

HIGH · 8.8 CVSS v3.1 Published 2026-05-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

ngrok versions 4.3.3 and 5.0.0-beta.2 contain a command injection vulnerability that allows attackers to execute arbitrary OS commands on the affected system, likely through unsanitized user input being passed to system shell commands.

MitigationUpgrade ngrok to the latest patched version immediately. If immediate upgrade is not feasible, restrict network access to the ngrok service and audit for any exposed attack surfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify ngrok is installed
    Run 'which ngrok' on Linux/macOS or check C:\Program Files\ngrok on Windows. Alternatively, run 'ngrok version' to see if the command is recognized.
    Affected if ngrok is not found on the system, then not affected by this CVE.
  2. Determine the installed ngrok version
    Run 'ngrok version' and note the exact version number displayed (e.g., 4.3.3, 5.0.0-beta.2, or another version).
    Affected if The installed version cannot be determined or differs from the reported versions.
  3. Compare against affected versions
    Check if the installed version matches exactly 4.3.3 or 5.0.0-beta.2. These are the specific versions known to contain the command injection flaw.
    Affected if The installed version is 4.3.3 or 5.0.0-beta.2, meaning the system is running a vulnerable version.
  4. Check for other affected versions within the range
    If the version is not an exact match to 4.3.3 or 5.0.0-beta.2, verify whether a newer patched version is available by checking the official ngrok releases page or release notes.
    Affected if Running an older or unspecified version and no patched version can be confirmed as installed.

A system is affected if ngrok version 4.3.3 or 5.0.0-beta.2 is installed and running, as these specific versions contain the command injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ngrok to the latest patched version immediately. If immediate upgrade is not feasible, restrict network access to the ngrok service and audit for any exposed attack surfaces.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57282 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-57282 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data