How severe is CVE-2025-11849?

No CVSS score has been assigned to CVE-2025-11849 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-11849?

CVE-2025-11849 affects the following packages: org.zwobble.mammoth:mammoth (Maven), mammoth (npm), Mammoth (NuGet), mammoth (PyPI). Ecosystems affected: Maven, npm, NuGet, PyPI.

How do I fix CVE-2025-11849?

Update org.zwobble.mammoth:mammoth to 1.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-11849 is resolved across your whole dependency graph.

How do I detect CVE-2025-11849 in my Maven, npm, NuGet, PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.zwobble.mammoth:mammoth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-11849 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2025-11849 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-11849 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-11849?

CVE-2025-11849 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 66th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-11849?

CVE-2025-11849 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-11849 published, and has it been updated?

CVE-2025-11849 was published on October 17, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2025-11849: mammoth — Fixed in 1.11.0

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-11849.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

mammothnpm

15.6Mdownloads / week

Description

Versions of the package mammoth from 0.3.25 and before 1.11.0; versions of the package mammoth from 0.3.25 and before 1.11.0; versions of the package mammoth before 1.11.0; versions of the package org.zwobble.mammoth:mammoth before 1.11.0 are vulnerable to Directory Traversal due to the lack of path or file type validation when processing a docx file containing an image with an external link (r:link attribute instead of embedded r:embed). The library resolves the URI to a file path and after reading, the content is encoded as base64 and included in the HTML output as a data URI. An attacker can read arbitrary files on the system where the conversion is performed or cause an excessive resources consumption by crafting a docx file that links to special device files such as /dev/random or /dev/zero.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.zwobble.mammoth:mammoth`	all versions	1.11.0`org.zwobble.mammoth:mammoth:1.11.0`
📦npm	`mammoth`	≥ 0.3.25&&< 1.11.0	1.11.0`npm install mammoth@1.11.0`
.NETNuGet	`Mammoth`	all versions	1.11.0`dotnet add package Mammoth --version 1.11.0`
🐍PyPI	`mammoth`	≥ 0.3.25&&< 1.11.0	1.11.0`pip install --upgrade 'mammoth==1.11.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.zwobble.mammoth:mammoth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.zwobble.mammoth:mammoth to 1.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-11849 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Versions of the package mammoth from 0.3.25 and before 1.11.0; versions of the package mammoth from 0.3.25 and before 1.11.0; versions of the package mammoth before 1.11.0; versions of the package org.zwobble.mammoth:mammoth before 1.11.0 are vulnerable to Directory Traversal due to the lack of path or file type validation when processing a docx file containing an image with an external link (r:link attribute instead of embedded r:embed). The library resolves the URI to a file path and after reading, the content is encoded as base64 and included in the HTML output as a data URI. An attacker ca

O3 Security · Impact-Aware SCA

Is CVE-2025-11849 in your dependencies?

Find it across Maven, npm, NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2025-11849 — mammoth