How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Attack vector: Network — reachable from anywhere that can route to the service.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: Low — an ordinary user account is enough.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: None.
- Integrity impact: None.
- Availability impact: High — total loss, or loss the attacker controls.
Weakness class
CVE-2024-45626 is classified as CWE-400: Uncontrolled Resource Consumption. A request can consume memory, CPU or storage without limit, exhausting capacity for everyone else.
Affected software
CVE-2024-45626 is recorded against 2 packages.
- james-server (from 3.8.0 up to 3.8.2)
- org.apache.james:james-server-jmap-draft (fixed in 3.7.6)
Timeline and source
Published on 6 February 2025 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
lists.apache.org
www.openwall.com
Other advisories for this package
james-server has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-400: Uncontrolled Resource Consumption) in other software:
