CVE-2026-46412
Malicious npm postinstall in @beproduct/nestjs-auth exfiltrates secrets (v0.1.2–0.1.19).
Is CVE-2026-46412 being exploited?
Not confirmed. CVE-2026-46412 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.77% probability of exploitation in the next 30 days.
How severe is CVE-2026-46412?
CVE-2026-46412 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46412?
Yes. A fix has been recorded for CVE-2026-46412. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46412 affect?
CVE-2026-46412 affects @beproduct/nestjs-auth v0.1.2-0.1.19, Node.js/npm dev machines, CI/CD runners, Developer workstations, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46412?
Remove affected versions, clear npm cache, install 0.1.20, rotate all creds, scan and reimage compromised hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Postinstall malware harvests npm/GitHub/OAuth/AWS/HashiCorp Vault tokens and env secrets; attackers can exfiltrate credentials, commit backdoors, and pivot to infra.
Immediate action required
- affected>= 0.1.2 and <= 0.1.19
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.