Object prototype modification via unsafe pointer tokens
Published Jul 9, 2026 · Updated Jul 9, 2026
Prototype pollution in APIDevTools JSON Schema $Ref Parser 15.3.0 through 15.3.5 allows remote authenticated users to modify Object.prototype. The $Refs.set and Pointer.set path walks attacker-controlled JSON Pointer tokens and performs nested assignments without rejecting proto, constructor, or prototype, allowing writes to inherited prototype objects. Reachability requires a consuming application to pass an attacker-controlled pointer and value into the public setter; resulting logic corruption, service interruption, or further application-specific impact depends on how polluted properties are used.
Summary
What happened
Prototype pollution in APIDevTools JSON Schema $Ref Parser 15.3.0 through 15.3.5 allows remote authenticated users to modify Object.prototype. The $Refs.set and Pointer.set path walks attacker-controlled JSON Pointer tokens and performs nested assignments without rejecting proto, constructor, or prototype, allowing writes to inherited prototype objects. Reachability requires a consuming application to pass an attacker-controlled pointer and value into the public setter; resulting logic corruption, service interruption, or further application-specific impact depends on how polluted properties are used.
The record
- CVE
- CVE-2026-15195
- Published
- Jul 9, 2026
- Updated
- Jul 9, 2026
- Vendor
- APIDevTools
- Product
- JSON Schema $Ref Parser
- Classifications
- CWE-94, CWE-1321
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2026CVE publishedPublication date reported by the CVE source.
- Jul 9, 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=15.3.0
- Affected versionversion=15.3.1
- Affected versionversion=15.3.2
- Affected versionversion=15.3.3
- Affected versionversion=15.3.4
- Affected versionversion=15.3.5
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
- GitHub issue 421 prototype-pollution demonstrationproof of concept · demonstrated
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