Prototype pollution via unsafe property dependency keys
Published Jul 17, 2026 · Updated Jul 17, 2026
Prototype pollution in sagold json-schema-library 11.5.0 through 11.5.1 allows remote authenticated users to modify Object.prototype. parsePropertyDependencies stores untrusted propertyDependencies keys in ordinary objects, so a proto key resolves to Object.prototype and a nested value becomes an inherited SchemaNode. Exploitation requires an application to enable the experimental propertyDependenciesKeyword and compile a user-controlled schema; resulting behavior depends on later inherited-property use.
Summary
What happened
Prototype pollution in sagold json-schema-library 11.5.0 through 11.5.1 allows remote authenticated users to modify Object.prototype. parsePropertyDependencies stores untrusted propertyDependencies keys in ordinary objects, so a proto key resolves to Object.prototype and a nested value becomes an inherited SchemaNode. Exploitation requires an application to enable the experimental propertyDependenciesKeyword and compile a user-controlled schema; resulting behavior depends on later inherited-property use.
The record
- CVE
- CVE-2026-16008
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- sagold
- Product
- json-schema-library
- Classifications
- CWE-1321, CWE-94
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=11.5.0
- Affected versionversion=11.5.1
What conditions does exploitation require?
What is affected?
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