Quick answers
- Is CVE-2026-33994 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33994 being exploited in the wild.
- How severe is CVE-2026-33994?
- Critical severity, with a CVSS score of 9.8, published 27 March 2026.
- Which products and versions are affected?
- locutus (npm) SEMVER:introduced=2.0.39,fixed=3.0.25.
- Is there a fix for CVE-2026-33994?
- Yes. locutus (npm): upgrade to 3.0.25 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-33994 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-33994?
- Check whether you run Locutus or locutus (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- locutus (npm): upgrade to 3.0.25 or later
npm install locutus@3.0.25
Technical details
The parse_str function in Locutus contains a prototype pollution vulnerability stemming from an incomplete fix for CVE-2026-25521. The previous patch replaced a String.prototype.includes()-based guard with RegExp.prototype.test(), but RegExp.prototype.test is itself a writable method that can be overridden. An attacker can bypass the guard by first polluting RegExp.prototype.test (via a separate prototype pollution gadget in another npm package) to always return false, then passing a crafted query string like '__proto__[polluted]=yes' to parse_str, allowing them to corrupt Object.prototype. The fix shipped in version 3.0.25 removes dependency on prototype methods and instead hardens the assignment sink itself using direct string comparisons that cannot be overridden.
Affected products
- Locutus Locutus 2.0.39 through 3.0.24
Identifiers
- CVE-2026-33994
- GHSA-vc8f-x9pp-wf5p
Timeline
- 2026-03-27: disclosed
- 2026-03-27: patched: Fixed in version 3.0.25
- 2026-03-27: advisory: GHSA-vc8f-x9pp-wf5p published