Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11849: Directory Traversal in mammoth

0
Medium
VulnerabilityCVE-2025-11849cvecve-2025-11849
Published: Fri Oct 17 2025 (10/17/2025, 05:00:06 UTC)
Source: CVE Database V5
Product: mammoth

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.

AI-Powered Analysis

AILast updated: 10/17/2025, 05:31:39 UTC

Technical Analysis

CVE-2025-11849 is a directory traversal vulnerability affecting the mammoth library, a tool used to convert DOCX files to HTML. The issue exists in versions up to 1.11.0 due to insufficient validation of the r:link attribute in DOCX image elements. Instead of embedded images (r:embed), the library processes external links by resolving the URI to a local file path. This allows an attacker to craft a malicious DOCX file containing image references to arbitrary files on the host system. When mammoth processes such a file, it reads the referenced file, encodes its content in base64, and embeds it in the HTML output. This can lead to unauthorized disclosure of sensitive files. Additionally, referencing special device files like /dev/random or /dev/zero can cause excessive resource consumption, potentially leading to denial of service. The vulnerability requires no privileges or authentication but does require user interaction to process the malicious DOCX file. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, user interaction needed, and high scope, with partial impact on confidentiality and availability. No known exploits have been reported yet, but the vulnerability poses a significant risk in environments that automatically process untrusted DOCX files.

Potential Impact

For European organizations, the impact includes potential exposure of sensitive internal files if attackers can submit malicious DOCX files for processing. This is particularly critical for enterprises that automate document ingestion or conversion workflows using mammoth, such as content management systems, web applications, or document processing pipelines. Confidentiality breaches could expose intellectual property, personal data, or configuration files. Resource exhaustion attacks could disrupt services, causing denial of service and impacting availability. Given the medium severity, the risk is moderate but can escalate if combined with other vulnerabilities or used in targeted attacks. Organizations handling sensitive documents or operating in regulated sectors (finance, healthcare, government) face increased compliance and reputational risks if exploited.

Mitigation Recommendations

1. Upgrade mammoth to version 1.11.0 or later where this vulnerability is fixed. 2. Implement strict validation and sanitization of DOCX files before processing, rejecting files with external image links or suspicious r:link attributes. 3. Run document conversion processes in isolated, sandboxed environments with minimal file system permissions to limit access to sensitive files. 4. Monitor and log document processing activities to detect anomalous file access patterns. 5. Employ rate limiting and resource usage controls to mitigate potential denial of service from resource exhaustion. 6. Educate users and administrators about the risks of processing untrusted DOCX files and enforce policies restricting document sources. 7. Consider using alternative libraries or tools with stronger security postures if mammoth is not essential.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
snyk
Date Reserved
2025-10-16T09:34:45.608Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68f1d13d9c34d0947ff86bfa

Added to database: 10/17/2025, 5:16:45 AM

Last enriched: 10/17/2025, 5:31:39 AM

Last updated: 10/19/2025, 8:25:19 AM

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats