Apache James
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Apache James.
By the Year
In 2025 there have been 2 vulnerabilities in Apache James with an average score of 7.5 out of ten. Last year, in 2024 James had 2 security vulnerabilities published. At the current rates, it appears that the number of vulnerabilities last year and this year may equal out.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2025 | 2 | 7.50 |
| 2024 | 2 | 0.00 |
| 2023 | 3 | 6.27 |
| 2022 | 6 | 6.80 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 1 | 9.80 |
It may take a day or so for new James vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Apache James Security Vulnerabilities
Apache James JMAP HTML-to-text unbounded memory pre-3.8.2/3.7.6
CVE-2024-45626
7.5 - High
- February 06, 2025
Apache James server JMAP HTML to text plain implementation in versions below 3.8.2 and 3.7.6 is subject to unbounded memory consumption that can result in a denial of service. Users are recommended to upgrade to version 3.7.6 and 3.8.2, which fix this issue.
Resource Exhaustion
Apache James DoS via IMAP Literals (v3.7.6,3.8.2 Mitigated)
CVE-2024-37358
7.5 - High
- February 06, 2025
Similarly to CVE-2024-34055, Apache James is vulnerable to denial of service through the abuse of IMAP literals from both authenticated and unauthenticated users, which could be used to cause unbounded memory allocation and very long computations Version 3.7.6 and 3.8.2 restrict such illegitimate use of IMAP literals.
Allocation of Resources Without Limits or Throttling
Apache James SMTP Smuggling <3.8.1, 3.7.5
CVE-2023-51747
- February 27, 2024
Apache James prior to versions 3.8.1 and 3.7.5 is vulnerable to SMTP smuggling. A lenient behaviour in line delimiter handling might create a difference of interpretation between the sender and the receiver which can be exploited by an attacker to forge an SMTP envelop, allowing for instance to bypass SPF checks. The patch implies enforcement of CRLF as a line delimiter as part of the DATA transaction. We recommend James users to upgrade to non vulnerable versions.
Improper Input Validation
Apache James <3.7.5/3.8.0 JMX deserialisation PrivEsc
CVE-2023-51518
- February 27, 2024
Apache James prior to version 3.7.5 and 3.8.0 exposes a JMX endpoint on localhost subject to pre-authentication deserialisation of untrusted data. Given a deserialisation gadjet, this could be leveraged as part of an exploit chain that could result in privilege escalation. Note that by default JMX endpoint is only bound locally. We recommend users to: - Upgrade to a non-vulnerable Apache James version - Run Apache James isolated from other processes (docker - dedicated virtual machine) - If possible turn off JMX
Marshaling, Unmarshaling
Apache James server version 3.7.3 and earlier provides a JMX management service without authentication by default
CVE-2023-26269
7.8 - High
- April 03, 2023
Apache James server version 3.7.3 and earlier provides a JMX management service without authentication by default. This allows privilege escalation by a malicious local user. Administrators are advised to disable JMX, or set up a JMX password. Note that version 3.7.4 onward will set up a JMX password automatically for Guice users.
AuthZ
Usage of temporary files with insecure permissions by the Apache James server
CVE-2022-45935
5.5 - Medium
- January 06, 2023
Usage of temporary files with insecure permissions by the Apache James server allows an attacker with local access to access private user data in transit. Vulnerable components includes the SMTP stack and IMAP APPEND command. This issue affects Apache James server version 3.7.2 and prior versions.
Exposure of Resource to Wrong Sphere
Unproper laxist permissions on the temporary files used by MIME4J TempFileStorageProvider may lead to information disclosure to other local users
CVE-2022-45787
5.5 - Medium
- January 06, 2023
Unproper laxist permissions on the temporary files used by MIME4J TempFileStorageProvider may lead to information disclosure to other local users. This issue affects Apache James MIME4J version 0.8.8 and prior versions. We recommend users to upgrade to MIME4j version 0.8.9 or later.
Cleartext Storage of Sensitive Information
Apache James prior to release 3.6.3 and 3.7.1 is vulnerable to a buffering attack relying on the use of the STARTTLS command
CVE-2022-28220
7.5 - High
- September 08, 2022
Apache James prior to release 3.6.3 and 3.7.1 is vulnerable to a buffering attack relying on the use of the STARTTLS command. Fix of CVE-2021-38542, which solved similar problem fron Apache James 3.6.1, is subject to a parser differential and do not take into account concurrent requests.
Command Injection
Fix of CVE-2021-40525 do not prepend delimiters upon valid directory validations
CVE-2022-22931
4.3 - Medium
- February 07, 2022
Fix of CVE-2021-40525 do not prepend delimiters upon valid directory validations. Affected implementations include: - maildir mailbox store - Sieve file repository This enables a user to access other users data stores (limited to user names being prefixed by the value of the username being used).
Directory traversal
Apache James ManagedSieve implementation alongside with the file storage for sieve scripts is vulnerable to path traversal
CVE-2021-40525
9.1 - Critical
- January 04, 2022
Apache James ManagedSieve implementation alongside with the file storage for sieve scripts is vulnerable to path traversal, allowing reading and writing any file. This vulnerability had been patched in Apache James 3.6.1 and higher. We recommend the upgrade. Distributed and Cassandra based products are also not impacted.
Directory traversal
In Apache James, while fuzzing with Jazzer the IMAP parsing stack, we discover
CVE-2021-40111
6.5 - Medium
- January 04, 2022
In Apache James, while fuzzing with Jazzer the IMAP parsing stack, we discover that crafted APPEND and STATUS IMAP command could be used to trigger infinite loops resulting in expensive CPU computations and OutOfMemory exceptions. This can be used for a Denial Of Service attack. The IMAP user needs to be authenticated to exploit this vulnerability. This affected Apache James prior to version 3.6.1. This vulnerability had been patched in Apache James 3.6.1 and higher. We recommend the upgrade.
Infinite Loop
In Apache James, using Jazzer fuzzer, we identified
CVE-2021-40110
7.5 - High
- January 04, 2022
In Apache James, using Jazzer fuzzer, we identified that an IMAP user can craft IMAP LIST commands to orchestrate a Denial Of Service using a vulnerable Regular expression. This affected Apache James prior to 3.6.1 We recommend upgrading to Apache James 3.6.1 or higher , which enforce the use of RE2J regular expression engine to execute regex in linear time without back-tracking.
Apache James prior to release 3.6.1 is vulnerable to a buffering attack relying on the use of the STARTTLS command
CVE-2021-38542
5.9 - Medium
- January 04, 2022
Apache James prior to release 3.6.1 is vulnerable to a buffering attack relying on the use of the STARTTLS command. This can result in Man-in -the-middle command injection attacks, leading potentially to leakage of sensible information.
Use of a Broken or Risky Cryptographic Algorithm
Apache PDFBox 2.0.14 does not properly initialize the XML parser, which
CVE-2019-0228
9.8 - Critical
- April 17, 2019
Apache PDFBox 2.0.14 does not properly initialize the XML parser, which allows context-dependent attackers to conduct XML External Entity (XXE) attacks via a crafted XFDF.
XXE
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Apache James or by Apache? Click the Watch button to subscribe.