Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-48161Published 2026-08-10

CVE-2026-48161 — dai-shi react18-use

critical (derived)

As of 2026-08-11, CVE-2026-48161 is a Critical-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in dai-shi react18-use, CVSS v4.0 9.3, EPSS 0.4% (34.6th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-48161 as of 2026-08-11; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
9.3/10Critical (derived)
EPSS
0.4%Higher than 34.6% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
6/10Threadlinqs triage score
Published
Updated 2026-08-11
CVSS v4.0 9.3 (Critical, derived from score) · EPSS 0.4% (higher than 34.6% of all scored CVEs) · Priority 6/10 · Published 2026-08-10

Last updated:

What is CVE-2026-48161?

react18-use is a React 19 use hook shim. Between 2026-05-19 01:07:01 and 2026-05-19 15:20:43, the default branch contained malicious commits 7b79148d1495a2505f9277da295a98cf176f4496 through 7b79148d1495a2505f9277da295a98cf176f4496 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-19 01:07:01 should treat the machine as compromised, rotate every credential the machine could reach, audit account activity since 2026-05-19 01:07:01, and clean local clones.

The record classifies CVE-2026-48161 under weakness class CWE-506. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 101 days ago.

Severity and exploitation probability

CVSS v4.0 base score
9.3 — Critical (derived from score)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS (FIRST)
0.4% probability of exploitation in the next 30 days, higher than 34.6% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-10

Is CVE-2026-48161 being exploited?

It currently carries a trending score of 38 in the Threadlinqs vulnerability feed.

Affected products and versions

  • dai-shi: react18-use

How to fix CVE-2026-48161

No vendor patch reference has been recorded for CVE-2026-48161 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-48161

No threat campaign in the Threadlinqs corpus currently references CVE-2026-48161, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch