Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted MIME message to parser
-
DeliveryMime4J parses input without resource limits
-
ExploitUnbounded memory/CPU allocation
-
ExecutionResource exhaustion on host
-
ImpactDenial of service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that an application use Apache James Mime4J Core or Dom prior to 0.8.15 to parse MIME messages supplied by an untrusted source (e.g. inbound email or user-uploaded message content). The core precondition is the absence of resource limits in the vulnerable versions, which the fix addresses by enforcing new limits and safer defaults; the specific message structure that triggers excessive allocation is not described in the available sources. Exploitation is limited by whether the embedding application actually exposes Mime4J parsing to attacker-controlled input - libraries parsing only trusted, internally generated messages are not realistically at risk. |
| Impact | This is a resource-exhaustion denial-of-service flaw (CWE-770, Allocation of Resources Without Limits or Throttling) in the Apache James Mime4J MIME-parsing library below 0.8.15, reported by Apache itself. No CVSS score or vector is provided in the input, so attack vector, complexity, and privilege requirements cannot be confirmed from a vendor- or NVD-assigned metric and are inferred only from the description (parsing of MIME messages). There is no EPSS score, no CISA KEV listing, and no public exploit referenced - the sole reference is an Apache mailing-list advisory thread, so exploitation status is: no public exploit identified at time of analysis. The vuln.today priority is 'this_week' rather than act_now/emergency, which is consistent with a non-actively-exploited availability-only issue. Realistic risk is moderate and bounded: the impact is availability loss, not code execution or data compromise, and exploitability depends entirely on whether the embedding application feeds attacker-controlled MIME messages into Mime4J. This is a genuine fix-this-week issue for mail-processing deployments but not a high-urgency, widely-weaponized emergency; the missing CVSS vector should be verified against the Apache advisory. |
| Exploit ScenarioDerived | An attacker sends a specially crafted MIME message (for example an email or an uploaded message blob) to an application that parses it with a vulnerable Mime4J version. Because the parser enforces no limits on resource allocation, processing the message consumes excessive memory or CPU, exhausting the host and denying service to legitimate users. No public exploit code is referenced, and the exact triggering structure is not described in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 06, 2026
Denial of service in Apache James Mime4J (Core and Dom modules) before 0.8.15: parsing attacker-supplied MIME messages can exhaust process resources because the vulnerable versions place no limits or throttling on resource allocation (CWE-770), and the 0.8.15 fix enforces new limits and safer defaults. Any Java application that passes untrusted inbound email or user-uploaded message content to the library is exposed, with the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5 High) reflecting impact limited to availability. The vendor advisory is published, but no public exploit code and no CISA KEV entry were identified at time of analysis.
RemediationAI
Upgrade Apache James Mime4J to 0.8.15, the version the vendor states fixes the issue by enforcing new limits and providing better defaults; both the Core and Dom artifacts must be moved to 0.8.15 or later, and dependency trees should be checked for transitive inclusions of older Mime4J releases. The vendor advisory is at https://lists.apache.org/thread.html/twktm00gmc8lt7tlqrrj16xw7kzbx16s. Where the upgrade cannot be applied immediately, exposure can only be reduced by removing attacker-controlled input from the vulnerable parsing path - i.e. restricting Mime4J parsing to trusted, internally generated messages and keeping untrusted inbound email or user-uploaded message content away from versions below 0.8.15 - which limits the attack surface but does not remove the unbounded-allocation behavior itself; the vendor's 0.8.15 limits and defaults remain the complete remediation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Mime4J is a standalone Java library for parsing and writing MIME messages, shipped as the Core and Dom artifacts and used by Apache James and by other Java mail servers, gateways and message-processing services that decode raw RFC 822/MIME input. The root cause is CWE-770, Allocation of Resources Without Limits or Throttling: pre-0.8.15 versions do not cap the resources consumed while parsing a message, so a crafted or simply oversized MIME message supplied by an untrusted source can drive consumption beyond what the hosting process can sustain, degrading or halting the parsing service. The fix in 0.8.15 addresses this by enforcing new limits and providing better defaults rather than by correcting a memory-safety defect; the specific message structure that triggers excessive allocation is not described in the available sources. Reachability is entirely a function of the embedding application: code paths that parse only trusted, internally generated messages do not expose the flaw, while services that parse inbound email or user-uploaded message content do. The published CPE identifiers for apache_james_mime4j_core and apache_james_mime4j_dom are wildcarded and therefore do not encode version boundaries; the affected range comes from the vendor statement that all versions prior to 0.8.15 are vulnerable.
Know when Apache James Mime4J Core gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
MIME messages are typically received from untrusted remote sources (AV:N, PR:N, UI:N); CWE-770 resource exhaustion yields availability-only impact (C:N/I:N/A:H), with scope unchanged.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
3DescriptionCVE.org
Allocation of Resources Without Limits or Throttling in Apache James Mime4J library prior version 0.8.15 allows Denial of Service upon parsing Mime messages. Users are recommended to upgrade to version 0.8.15 which fixes the issue by enforcing new limits and providing better defaults.
Articles & Coverage 1
Executive ViewAI
Apache James Mime4J versions before 0.8.15 are vulnerable to a denial-of-service attack that can be triggered by processing malicious MIME messages, potentially disrupting email or file-upload services for internal and external users. No public exploit code or active exploitation has been identified, but the availability of a patch for the library is critical to restore resilience. Leadership should prioritize upgrading affected systems to prevent service outages.
No vendor-released patch identified at time of analysis. Interim mitigations include implementing strict input validation and size limits on incoming MIME messages, throttling resource allocation, and monitoring for abnormal resource consumption.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-118221
GHSA-7j7p-grhm-j8xq
NVD
CVE.org
EPSS
Exploit-DB