CVE-2026-48160

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: None knownExposed: 0

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

react-tracked provides state usage tracking with Proxies. Between 2026-05-18 19:26:36 and 2026-05-19 15:22:45, the default branch contained malicious commits 6978272a7d6ca02225cb747ea69f427512e33699 through 949f1a3d6bb1ff7d1a0dec892afd773e742627e8 that executed remote attacker-controlled code on developer machines during npm install. The commits were removed by force-push, but local clones, forks, and direct-SHA URLs may still contain them, and npm install against an affected checkout will still execute the code today. The package was not published to npm. src/install.js was added and wired into the postinstall script. It fetched a JavaScript payload from an attacker-controlled HTTPS endpoint (configurable via an environment variable), disabled TLS verification, and evaluated the response as code with require available. Execution was deliberately skipped on CI and cloud/serverless environments, targeting developer workstations. The second-stage payload was attacker-hosted and cannot be reconstructed. Assume full compromise of anything reachable from a Node process with the user's permissions. Those who ran npm install against an affected checkout on a developer machine on or after 2026-05-18 19:26:36 should treat the machine as compromised, rotate every credential the machine could reach, audit account activity** since 2026-05-18 19:26:36, and clean local clones.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
57(Track)
EG Risk 57/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
Severity93% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 11, 2026

Advisory Details (1)

Auto-updated Aug 23, 2026
Patch available. Sources: github.
github Patch Available

Malicious code execution via compromised commits · Advisory · dai-shi/react-tracked · GitHub

https://github.com/dai-shi/react-tracked/security/advisories/GHSA-79c5-q7m9-9c6x

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 31× 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-25 17:15 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 17:35 UTCEG score recompute
  4. 2026-08-24 09:58 UTCEG score recompute
  5. 2026-08-23 03:11 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 00:32 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 01:42 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 18:42 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 17:24 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 17:09 UTCEG score recompute
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 18:18 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 03:05 UTCEG score recompute
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 04:17 UTCEG score recompute
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 01:41 UTCEG score recompute
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-12 15:27 UTCEG score recompute
Show 6 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 16:36 UTCEG score recompute
  3. 2026-08-11 16:06 UTCEG score recompute
  4. 2026-08-10 21:31 UTCEG score recompute
  5. 2026-08-10 21:15 UTCEG score recompute
  6. 2026-08-10 21:14 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-48160?
CVE-2026-48160 is a critical vulnerability published on August 10, 2026. react-tracked provides state usage tracking with Proxies. Between 2026-05-18 19:26:36 and 2026-05-19 15:22:45, the default branch contained malicious commits 6978272a7d6ca02225cb747ea69f427512e33699 through 949f1a3d6bb1ff7d1a0dec892afd773e742627e8 that executed remote attacker-controlled code on…
When was CVE-2026-48160 disclosed?
CVE-2026-48160 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48160 actively exploited?
CVE-2026-48160 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 67.5% of all scored CVEs.
What is the CVSS score of CVE-2026-48160?
CVE-2026-48160 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-48160?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48160, 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-48160

Explore →

Is Your Infrastructure Affected by CVE-2026-48160?

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

Start Free Scan →Browse All CVEs