CVE-2025-11849 — mammoth
Fix: mwilliamson/mammoth.js@c54aaebCVE-2025-11849 is a Path Traversal vulnerability in org.zwobble.mammoth:mammoth. A fix is available for org.zwobble.mammoth:mammoth — see the affected versions and patch details below.
Mammoth is vulnerable to Directory Traversal
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
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.
mammothnpmDescription
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.zwobble.mammoth:mammoth | all versions | 1.11.0org.zwobble.mammoth:mammoth:1.11.0 |
| 📦npm | mammoth | ≥ 0.3.25&&< 1.11.0 | 1.11.0npm install mammoth@1.11.0 |
| .NETNuGet | Mammoth | all versions | 1.11.0dotnet add package Mammoth --version 1.11.0 |
| 🐍PyPI | mammoth | ≥ 0.3.25&&< 1.11.0 | 1.11.0pip install --upgrade 'mammoth==1.11.0' |
Detection & mitigation playbook
Open-source dependencyDetect
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-11849 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-11849. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-11849 in your dependencies?
O3 Security finds CVE-2025-11849 across Maven, npm, NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.