Prototype method deletion via crafted property paths
Published Jan 21, 2026 · Updated Aug 27, 2026
Prototype pollution in Lodash 4.0.0 through 4.17.22 allows attackers to delete inherited methods through crafted property paths. The _.unset and _.omit path traversal resolves constructor.prototype segments to global prototypes and deletes the selected property instead of rejecting the path. Exploitation requires a consuming application to pass attacker-controlled paths; it deletes existing prototype properties but does not replace their behavior.
Summary
What happened
Prototype pollution in Lodash 4.0.0 through 4.17.22 allows attackers to delete inherited methods through crafted property paths. The _.unset and _.omit path traversal resolves constructor.prototype segments to global prototypes and deletes the selected property instead of rejecting the path. Exploitation requires a consuming application to pass attacker-controlled paths; it deletes existing prototype properties but does not replace their behavior.
The record
- CVE
- CVE-2025-13465
- Published
- Jan 21, 2026
- Updated
- Aug 27, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Quay
- Classifications
- CWE-1321, CAPEC-180
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo