CVE-2026-25521: locutus is vulnerable to Prototype Pollution
(updated )
A Prototype Pollution vulnerability exists in the the npm package locutus (>2.0.12). Despite a previous fix that attempted to mitigate Prototype Pollution by checking whether user input contained a forbidden key, it is still possible to pollute Object.prototype via a crafted input using String.prototype. This issue was fixed in version 2.0.39.
References
- access.redhat.com/security/cve/CVE-2026-25521
- bugzilla.redhat.com/show_bug.cgi?id=2436950
- github.com/advisories/GHSA-rxrv-835q-v5mh
- github.com/locutusjs/locutus/commit/042af9ca7fde2ff599120783e720a17f335bb01c
- github.com/locutusjs/locutus/security/advisories/GHSA-rxrv-835q-v5mh
- nvd.nist.gov/vuln/detail/CVE-2026-25521
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25521.json
Code Behaviors & Features
Detect and mitigate CVE-2026-25521 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →