CVE-2026-48161Known exploitationNetwork attack vector

Arbitrary code execution via malicious postinstall hook

Published Aug 10, 2026 · Updated Aug 10, 2026

Malicious postinstall code in react18-use commit 7b79148d1495a2505f9277da295a98cf176f4496 allows remote attackers to execute code during npm install. The src/install.js postinstall hook disables TLS verification, fetches JavaScript from an attacker-controlled HTTPS endpoint, and evaluates it with require available. Execution requires npm install from the affected checkout on a developer workstation; CI and cloud or serverless environments are skipped, and the Node process's user permissions bound the compromise.

CVSS severityUnavailable
Unscored
EPSS probability0.42%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Malicious postinstall code in react18-use commit 7b79148d1495a2505f9277da295a98cf176f4496 allows remote attackers to execute code during npm install. The src/install.js postinstall hook disables TLS verification, fetches JavaScript from an attacker-controlled HTTPS endpoint, and evaluates it with require available. Execution requires npm install from the affected checkout on a developer workstation; CI and cloud or serverless environments are skipped, and the Node process's user permissions bound the compromise.

The record

CVE
CVE-2026-48161
Published
Aug 10, 2026
Updated
Aug 10, 2026
Vendor
Daishi Kato
Product
react18-use
Classifications
T1059.007, T1195.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 19, 2026Exploitation reportedMalicious react18-use repository compromise
  2. Aug 10, 2026CVE publishedPublication date reported by the CVE source.
  3. Aug 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 7b79148d1495a2505f9277da295a98cf176f4496, <= 7b79148d1495a2505f9277da295a98cf176f4496

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Daishi Kato · react18-useversion=>= 7b79148d1495a2505f9277da295a98cf176f4496, <= 7b79148d1495a2505f9277da295a98cf176f4496

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationReported
Public exploitUnconfirmed

Weakness, pattern, technique

T1059.007JavaScript/JScript
T1195.001Compromise Software Dependencies and Development Tools

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo