In Apache James server prior version 3.9.1 improper Access Control List processing is exposed by the JMAP protocol
Source GCVE Database
Not known to be exploited : upgrade to 3.9.1 soon.
Data as of 6 Nov 2026, 13:24 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.9.1
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade Apache James and org.apache.james/apache-james-server to 3.9.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache James | Affected
| Fixed in
|
Mavenorg.apache.james/apache-james-serverpkg:maven/org.apache.james/apache-james-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users are advised to upgrade Apache James server to version 3.9.1, which contains the official fix for this ACL processing vulnerability. No additional mitigation steps are indicated.
Description
Apache James server versions prior to 3.9.1 have an improper Access Control List (ACL) processing vulnerability in the JMAP protocol. This flaw arises because the JMAP protocol does not correctly handle negative ACL rules set by the IMAP protocol, allowing users to administer folders despite explicit denial of rights in IMAP. Upgrading to version 3.9.1 resolves this issue.