This weekExploitable · Confirmed
mammoth, org.zwobble.mammoth:mammoth: Mammoth is vulnerable to Directory Traversal
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- mammoth (npm): from 0.3.25, before 1.11.0
- org.zwobble.mammoth:mammoth (Maven): every version, before 1.11.0
- mammoth (PyPI): from 0.3.25, before 1.11.0
- Mammoth (NuGet): every version, before 1.11.0
- mammoth (PyPI): from 0.3.25, before 1.11.0
The fix
mammoth (npm) fixed in 1.11.0
npmnpm install mammoth@1.11.0pnpmpnpm add mammoth@1.11.0yarnyarn add mammoth@1.11.0bunbun add mammoth@1.11.0Check what is installednpm ls mammothPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency mammoth to 1.11.0 or the nearest later release, to fix CVE-2025-11849. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.org.zwobble.mammoth:mammoth (Maven) fixed in 1.11.0
mavenmvn versions:use-dep-version -Dincludes=org.zwobble.mammoth:mammoth -DdepVersion=1.11.0 -DforceVersion=trueCheck what is installedmvn dependency:tree -Dincludes=org.zwobble.mammoth:mammothPaste into Cursor, Lovable or Claude CodeUpgrade the Maven dependency org.zwobble.mammoth:mammoth to 1.11.0 or the nearest later release, to fix CVE-2025-11849. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.mammoth (PyPI) fixed in 1.11.0
pippython -m pip install mammoth==1.11.0uvuv add mammoth==1.11.0poetrypoetry add mammoth@1.11.0Check what is installedpython -m pip show mammothPaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency mammoth to 1.11.0 or the nearest later release, to fix CVE-2025-11849. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.Mammoth (NuGet) fixed in 1.11.0
dotnetdotnet add package Mammoth --version 1.11.0Check what is installeddotnet list packagePaste into Cursor, Lovable or Claude CodeUpgrade the NuGet dependency Mammoth to 1.11.0 or the nearest later release, to fix CVE-2025-11849. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))