CVE-2026-48159: use-reducer-async was vulnerable to malicious code execution via compromised commits

Published Aug 10, 2026
·
Updated

use-reducer-async is a React useReducer with async actions. Between 2026-05-18 16:29:52 and 2026-05-19 15:26:07, the default branch contained malicious commits da72edbde5705efcec6c62e0a3dcb73687b78dc8 through df07d5711458d8b46e11dd7afaaa21e88cafabfb 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 16:29:52 should treat the machine as compromised, rotate every credential the machine could reach, audit account activity since 2026-05-18 16:29:52, and clean local clones.

Affected Software

1 affected component
npm/use-reducer-async

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Operational

    Treat any developer machine that ran `npm install` against an affected checkout on or after 2026-05-18 16:29:52 as compromised.

  2. Operational

    Rotate every credential that the compromised developer machine could reach.

  3. Operational

    Audit account activity since 2026-05-18 16:29:52 on systems/accounts reachable by the compromised developer machines.

  4. Operational

    Clean local clones/forks/direct-SHA checkouts that may still contain the malicious commits (da72edbde5705efcec6c62e0a3dcb73687b78dc8 through df07d5711458d8b46e11dd7afaaa21e88cafabfb) and re-clone from the corrected branch.

Event History

Aug 10, 2026
CVE Published
via MITRE·05:55 PM
Data Sourced
via MITRE·05:55 PM
DescriptionWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-48159?

CVE-2026-48159 has a risk rating of 89.

2

What kind of vulnerability is CVE-2026-48159?

CVE-2026-48159 is a vulnerability that allows for malicious code execution via compromised commits.

3

Who is affected by CVE-2026-48159?

Users of the npm/use-reducer-async package who pulled from the default branch during the specified date range are affected by CVE-2026-48159.

4

How did CVE-2026-48159 occur?

CVE-2026-48159 occurred due to malicious commits added to the default branch of use-reducer-async between May 18 and May 19, 2026.

5

How do I fix CVE-2026-48159?

To fix CVE-2026-48159, update your use-reducer-async package to the latest secure version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203