CVE-2025-11849
CVE-2025-11849 is a Path Traversal vulnerability in org.zwobble.mammoth:mammoth. O3 Security confirms whether CVE-2025-11849 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Mammoth is vulnerable to Directory Traversal
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
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.0 |
| 📦npm | mammoth | ≥ 0.3.25&&< 1.11.0 | 1.11.0 |
| .NETNuGet | Mammoth | all versions | 1.11.0 |
| 🐍PyPI | mammoth | ≥ 0.3.25&&< 1.11.0 | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether CVE-2025-11849 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
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 detects CVE-2025-11849 across Maven, npm, NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.