CVE-2025-13158: apidoc-core has a prototype pollution vulnerability

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 0.5%, percentile 42: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 42% of all scored CVEs (low). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes apidoc-core (npm) >= 0.2.0, <= 0.15.0, no fixed version listed. Check your lockfile, including transitive dependencies.

What it is

Prototype pollution vulnerability in apidoc-core versions 0.2.0 and all subsequent versions allows remote attackers to modify JavaScript object prototypes via malformed data structures, including the “define” property processed by the application, potentially leading to denial of service or unintended behavior in applications relying on the integrity of prototype chains. This affects the preProcess() function in apigroup.js, apiparamtitle.js, apiuse.js, and apipermission.js worker modules.

From the GitHub advisory

Prototype pollution vulnerability in apidoc-core versions 0.2.0 and all subsequent versions allows remote attackers to modify JavaScript object prototypes via malformed data structures, including the “define” property processed by the application, potentially leading to denial of service or unintended behavior in applications relying on the integrity of prototype chains. This affects the preProcess() function in apigroup.js, apiparamtitle.js, apiuse.js, and apipermission.js worker modules.

Weakness type: CWE-1321.

Product: apidoc-core (npm) · Assigned by: Sonatype · Published: 2025-12-26

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Attack requirements: none
• Privileges required: none (no login)
• User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.50% probability of exploitation activity in the next 30 days; percentile 42.

Timeline

• 2025-12-26 — CVE record last updated
• 2025-12-26 — CVE record published by Sonatype
• 2025-12-26 — GitHub-reviewed advisory GHSA-6vj3-p34w-xxjp published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-6vj3-p34w-xxjp github.com
2. CVE.org record CVE-2025-13158 cve.org
3. NVD entry CVE-2025-13158 nvd.nist.gov

Other references from the CVE record and advisory

1. sonatype.com sonatype.com

Critical npm advisories · Today’s Security Digest