Prototype pollution via crafted define structures
Published Dec 26, 2025 · Updated Dec 26, 2025
Prototype pollution in apiDoc apidoc-core 0.2.0 and later allows remote attackers to alter object prototypes through crafted parser data. The preProcess() functions in four worker modules process attacker-controlled define structures, but the published advisories do not identify the specific unsafe assignment or merge operation. No authentication or user interaction is required; exploitation can interrupt processing or alter applications that rely on intact prototype chains.
Summary
What happened
Prototype pollution in apiDoc apidoc-core 0.2.0 and later allows remote attackers to alter object prototypes through crafted parser data. The preProcess() functions in four worker modules process attacker-controlled define structures, but the published advisories do not identify the specific unsafe assignment or merge operation. No authentication or user interaction is required; exploitation can interrupt processing or alter applications that rely on intact prototype chains.
The record
- CVE
- CVE-2025-13158
- Published
- Dec 26, 2025
- Updated
- Dec 26, 2025
- Vendor
- apiDoc
- Product
- apidoc-core
- Classifications
- CWE-1321, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 2025CVE publishedPublication date reported by the CVE source.
- Dec 26, 2025Record 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=0.2.0 <*
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