Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.4amended

ngrok is Vulnerable to Command Injection

CVE-2025-57282GHSA-qr28-p3wr-mxq3

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm ngrok

    Affected
    >= 4.3.3, <= 4.3.3>= 5.0.0-beta.2, <= 5.0.0-beta.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.4 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P · score source
EPSS
  • CVE-2025-57282: 0.98% estimated exploitation activity in the next 30 days; percentile 62.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-qr28-p3wr-mxq3

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-qr28-p3wr-mxq3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-57282

Advisory: ngrok is Vulnerable to Command Injection
IDs: CVE-2025-57282, GHSA-qr28-p3wr-mxq3
Record: https://patchnext.com/advisories/cve-2025-57282 (revision 3, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm ngrok: affected >= 4.3.3, <= 4.3.3; >= 5.0.0-beta.2, <= 5.0.0-beta.2

## Suggested inspection (read-only)
- `npm ls ngrok --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ngrok.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-qr28-p3wr-mxq3 (OSV record GHSA-qr28-p3wr-mxq3 lists affected ranges: npm ngrok >=4.3.3 =5.0.0-beta.2 <=5.0.0-beta.2)
- Verified: https://github.com/advisories/GHSA-qr28-p3wr-mxq3 (GitHub-reviewed advisory GHSA-qr28-p3wr-mxq3 lists affected ranges: npm ngrok >=4.3.3 =5.0.0-beta.2 <=5.0.0-beta.2)

Commands are suggestions: review each one before running it.

Loading voting…