Loading vulnerability…
In pnpm versions 10.26.2 and below, HTTP/HTTPS tarball dependencies (and git-hosted tarballs) are recorded in the pnpm lockfile without integrity hashes. As a result, even when a lockfile is committed, pnpm cannot verify that the fetched tarball content matches a previously-resolved artifact. A remote server hosting the tarball can therefore serve different content on different installs while still satisfying the same lockfile entry, enabling a lockfile integrity bypass for URL/git tarball dependencies.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A pnpm PackageGate zero-day that can be exploited to bypass security controls intended to prevent automatic execution of lifecycle scripts (e.g., when using --ignore-scripts) and/or defeat lockfile integrity expectations during package installation.
A pnpm vulnerability (one of two referenced) fixed by pnpm; discussed in the context of PackageGate bypasses affecting JavaScript package managers, including bypass of script-execution protections and (for pnpm) lockfile integrity bypass.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.