# CVE-2025-13158: apidoc-core - prototype pollution in api_group.js, api_param_title.js, api_use.js, and api_permission.js worker

> Remote attackers can pollute JavaScript object prototypes via malformed data, causing denial of service or unintended behavior in applications using apidoc-core.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2025
- **Updated:** 26 Dec 2025
- **Also known as:** GHSA-6vj3-p34w-xxjp

## What is CVE-2025-13158?

CVE-2025-13158 is a critical vulnerability in apidoc-core, published on 26 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 api_group.js, api_param_title.js, api_use.js, and api_permission.js worker modules.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2025-13158?

2 open source packages ship an affected version, including apidoc-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apidoc-core` | npm | From 0.2.0 to 0.15.0 | None |
| `apidoc-core` | npm | From 0.2.0 to 0.15.0 | None |

## How do I fix CVE-2025-13158?

No fix has been published for CVE-2025-13158 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13158 being exploited?

There is no known exploitation of CVE-2025-13158 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13158 and fix it if it is affected.

What it is: CVE-2025-13158 is a critical vulnerability in apidoc-core, published on 26 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13158 in the wild and no public exploit code.

Affected packages and fixed versions:
- apidoc-core (npm): affected from 0.2.0 up to 0.15.0; no fix listed
- apidoc-core (npm): affected from 0.2.0 up to 0.15.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13158/ (Markdown: https://insights.sbomify.com/CVE-2025-13158/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13158
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13158
- OSV: https://osv.dev/vulnerability/CVE-2025-13158

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13158/
Summaries are generated and may contain mistakes; the official description above is the record.