CVE-2026-74756: Apache James · Insecure Default
Affects Apache JamesSource CVE Database V5
Not known to be exploited : upgrade to 3.9.1 soon.
Data as of 6 Nov 2026, 12:04 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
Upgrade Apache James to version 3.9.1 or later, where the issue is fixed by setting a random credential by default on unprotected webadmin endpoints. This official fix prevents unauthorized public access without requiring additional configuration.
Description
Apache James versions prior to 3.9.1 shipped docker-compose configurations that exposed the Webadmin REST API publicly without proper authentication, creating a security risk. Starting with version 3.9.1, a random credential is set by default on unprotected webadmin endpoints to mitigate this issue while maintaining usability.