Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as James user
-
DeliveryTarget folder denied via IMAP negative ACL
-
ExploitSend JMAP folder-administration request
-
ExecutionJMAP skips negative rule check
-
ImpactAdminister restricted mailbox folder
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires: (1) the JMAP protocol enabled and reachable on the Apache James server (versions 3.9.0 up to, but not including, 3.9.1); (2) an attacker holding a valid, authenticated James account; and (3) an existing IMAP ACL negative ('deny') rule that explicitly revoked that user's administration right on a target folder. The flaw is that JMAP's ACL processing does not account for IMAP-positioned negative rules, so the denial is silently ignored over JMAP. Limiting factors: this only matters in multi-user/shared-folder deployments that actually use IMAP negative ACL rules - single-user installs or deployments that never set deny rules are not meaningfully affected; the attacker must already be authenticated and have a prior relationship to the folder (a denied grant), so it is not a path for an anonymous outsider. |
| Impact | Signals are consistent in pointing to a real-but-non-emergency issue. The vendor CVSS of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) looks severe, but it conflicts internally with the description: the flaw lets 'users' who were explicitly denied rights via IMAP act anyway, which implies authenticated users (PR:L) rather than PR:N, and the impact is folder administration (an integrity/authorization effect) rather than the pure C:H/I:N the vendor assigned - verify the authentication precondition and impact mapping with Apache. EPSS is low at 0.20% (10th percentile), there is no CISA KEV listing, and no public exploit code was supplied (the references are Apache/oss-security advisory threads, not weaponized PoC), so the probability of imminent widespread exploitation is low. The vuln.today decision label is 'this_week,' not act_now or emergency, which aligns with: a straightforward logic bug (low attack complexity) that is nonetheless gated behind needing an authenticated account and a specific IMAP negative-ACL configuration. Net: a genuine authorization-bypass worth patching on a normal cycle, not a high-CVSS-but-illusory issue, but also not evidence of active, automatable mass exploitation. |
| Exploit ScenarioDerived | An authenticated Apache James user who has been explicitly denied administrative rights on a shared mailbox folder through an IMAP negative ACL rule connects over JMAP instead. Because JMAP ignores the IMAP negative rule, the user issues JMAP folder-administration operations and manages the folder they were supposed to be locked out of. No public exploit code was identified at time of analysis; the trigger is a protocol-handling inconsistency rather than a memory-corruption bug. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Nov 10, 2026
Authorization bypass in Apache James 3.9.0 allows an authenticated user to administer folders over JMAP even when an IMAP negative ACL rule explicitly denies that right; the issue is fixed in 3.9.1. Exploitation requires JMAP to be enabled and reachable, a valid James account, and a pre-existing IMAP deny rule on a shared folder, so single-user installs or deployments that never set negative ACL rules are not meaningfully exposed. No public exploit was identified at time of analysis; EPSS is 0.20% (10th percentile).
Earlier versions of this analysis (1)
Apache James server before 3.9.1 allows an authenticated user to administer folders in a shared mailbox over JMAP even where an IMAP negative ACL rule explicitly denies that user the right, because the JMAP access-control path does not account for negative rules positioned via IMAP. Exploitation requires valid credentials, JMAP enabled and reachable, and a shared mailbox carrying an explicit IMAP deny rule for that account, so this is a privilege-boundary bypass among existing users rather than anonymous access; the supplied CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) scores 5.4 with low confidentiality and integrity impact only. No public exploit code and no CISA KEV entry were identified at time of analysis, and the vendor-released fix is version 3.9.1.
RemediationAI
Upgrade Apache James to 3.9.1, the vendor-released fixed version; the vendor advisory states that upgrading to 3.9.1 fixes this issue (https://lists.apache.org/thread.html/7qwsmkk88xbfq4q9o0pz9bt8p9p1yjs7). Patch availability is confirmed from the vendor. No other vendor-specified workaround is provided in the available data, so affected deployments should apply the 3.9.1 update and then verify that JMAP ACL enforcement honors IMAP negative rules in shared-folder deployments.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache James is a Java-based mail server that exposes both IMAP and JMAP. Its ACL model lets users and administrators grant or deny folder rights, and CVE-2026-49939 arises because JMAP's ACL processing does not account for negative ('deny') rules positioned through IMAP. CWE-284 (Improper Access Control) captures the root cause: inconsistent authorization enforcement across protocol handlers, so a user with a valid account and a denied grant can still perform folder administration through JMAP. The supplied sources do not describe the exact code path or the full set of JMAP operations affected; the CPE cpe:2.3:a:apache_software_foundation:apache_james:*:*:*:*:*:*:*:* is broad, while EUVD identifies Apache James 3.9.0 <3.9.1 as affected.
Know when Apache James 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:H/I:N/A:N
Authenticated user bypasses a denied IMAP ACL (PR:L), network JMAP with no special complexity (AV:N/AC:L), gaining folder administration (I:H, incidental read C:L).
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
3DescriptionCVE.org
In Apache James server prior version 3.9.1 improper Access Control List processing is exposed by the JMAP protocol which do not account for negative rules positionned by IMAP protocol.
This results in users being able to administer folders in JMAP despite having being explicitly denied the right to do so in IMAP.
Users are recommended to upgrade to version 3.9.1 which fixes this issue.
Executive ViewAI
A high-severity authorization bypass in Apache James 3.9.0 (CVE-2026-49939) allows authenticated users to administer shared folders via JMAP despite explicit IMAP deny rules, potentially compromising folder-level security controls. This affects only deployments with JMAP enabled and negative ACL rules configured; single-user or rule-free environments are not meaningfully exposed, but organizations relying on these controls should prioritize patching.
Apply vendor patch.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Apache James
View allPath traversal in Apache James's SieveFileRepository lets a logged-in mail user write SIEVE scripts outside their own di
Denial of service in Apache James MIME4J before 0.8.15 allows unauthenticated remote attackers to consume unbounded serv
Insufficient verification of the JWT audience claim in Apache James 3.9.0 (and earlier releases before 3.9.1) lets a hol
Apache James deployments built from the project's shipped docker-compose file expose the Webadmin REST API to the networ
Server-side request forgery in Apache James server (all versions prior to 3.9.1) lets an authenticated JMAP user reach i
EUVD-2026-118216
GHSA-84j6-j2xp-crm8
NVD
CVE.org
EPSS
Exploit-DB