CVE-2026-57998

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

better-npm-audit through 3.11.0, and the 4.0.0-rc.2 prerelease, builds its npm audit command by interpolating the user-supplied --registry option into a command string in src/handlers/handleInput.ts without validation or quoting, then passes that string to child_process.exec() in index.ts, which spawns a shell. A registry value containing shell metacharacters such as a semicolon, pipe, or command substitution executes arbitrary operating system commands with the privileges of the process running the audit.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
51(Track*)
EG Risk 51/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 29, 2026

Advisory Details (6)

Auto-updated Aug 22, 2026
🔬 Proof of concept available. No patch confirmed yet. Sources: github_pr.
generic

better-npm-audit OS Command Injection via registry flag | Advisories | VulnCheck

https://www.vulncheck.com/advisories/better-npm-audit-os-command-injection-via-registry-flag
github_pr

Implement registry URL validation in handleInput

Upstream fix in progress (PR #120 · jeemok/better-npm-audit, state=open)

https://github.com/jeemok/better-npm-audit/pull/120
generic

better-npm-audit/index.ts at fd99a0f41ff4342b8a0a6fdbe5a17261de3d0544 · jeemok/better-npm-audit · GitHub

https://github.com/jeemok/better-npm-audit/blob/fd99a0f41ff4342b8a0a6fdbe5a17261de3d0544/index.ts#L34
generic

better-npm-audit/src/handlers/handleInput.ts at fd99a0f41ff4342b8a0a6fdbe5a17261de3d0544 · jeemok/better-npm-audit · GitHub

https://github.com/jeemok/better-npm-audit/blob/fd99a0f41ff4342b8a0a6fdbe5a17261de3d0544/src/handlers/handleInput.ts#L30-L37
generic

GitHub - jeemok/better-npm-audit: The goal of this project is to provide additional features on top of the existing npm audit options · GitHub

https://github.com/jeemok/better-npm-audit
generic🟡 PoC Available

[CRITICAL] Remote Code Execution via Command Injection in --registry Flag · Issue #119 · jeemok/better-npm-audit · GitHub

https://github.com/jeemok/better-npm-audit/issues/119

Vendor Advisories for CVE-2026-57998(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 30× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 23:14 UTCGHSA enrichment
  3. 2026-08-29 12:07 UTCEG score recompute
  4. 2026-08-29 12:06 UTCGHSA enrichment
  5. 2026-08-29 01:01 UTCEG score recompute
  6. 2026-08-29 01:01 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 11:55 UTCGHSA enrichment
  9. 2026-08-28 00:50 UTCEG score recompute
  10. 2026-08-28 00:50 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 13:46 UTCGHSA enrichment
  13. 2026-08-27 02:41 UTCGHSA enrichment
  14. 2026-08-26 15:37 UTCEG score recompute
  15. 2026-08-26 15:36 UTCGHSA enrichment
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-26 04:29 UTCEG score recompute
  18. 2026-08-26 04:29 UTCGHSA enrichment
  19. 2026-08-25 17:25 UTCEG score recompute
  20. 2026-08-25 17:25 UTCGHSA enrichment
  21. 2026-08-25 17:01 UTCEG score recompute
  22. 2026-08-25 17:00 UTCGHSA enrichment
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-25 07:49 UTCGHSA enrichment
  25. 2026-08-24 20:45 UTCEG score recompute
Show 10 more
  1. 2026-08-24 20:45 UTCGHSA enrichment
  2. 2026-08-24 09:41 UTCEG score recompute
  3. 2026-08-24 09:41 UTCGHSA enrichment
  4. 2026-08-23 22:36 UTCGHSA enrichment
  5. 2026-08-23 11:30 UTCGHSA enrichment
  6. 2026-08-23 00:26 UTCEG score recompute
  7. 2026-08-23 00:26 UTCGHSA enrichment
  8. 2026-08-22 13:21 UTCEG score recompute
  9. 2026-08-22 12:46 UTCEG score recompute
  10. 2026-08-22 12:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57998?
CVE-2026-57998 is a high vulnerability published on August 22, 2026. better-npm-audit through 3.11.0, and the 4.0.0-rc.2 prerelease, builds its npm audit command by interpolating the user-supplied --registry option into a command string in src/handlers/handleInput.ts without validation or quoting, then passes that string to child_process.exec() in index.ts, which…
When was CVE-2026-57998 disclosed?
CVE-2026-57998 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57998 actively exploited?
CVE-2026-57998 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.9% of all scored CVEs.
What is the CVSS score of CVE-2026-57998?
CVE-2026-57998 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-57998?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57998, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57998

Explore →

Is Your Infrastructure Affected by CVE-2026-57998?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs