CVE-2026-76171: Apache James · Server-Side Request Forgery
Affects Apache JamesSource CVE Database V5
Not known to be exploited : upgrade to 3.9.1 soon.
Data as of 6 Nov 2026, 12:03 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 to 3.9.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache James | Affected
| Fixed in
|
AI-suggested
Users should upgrade Apache James to version 3.9.1 or later, where this SSRF vulnerability has been fixed. No other mitigation actions are specified or required.
Description
Apache James server versions 3.9.0 up to but not including 3.9.1 contain a server-side request forgery (SSRF) vulnerability in the JMAP webPush validation. This flaw allows an attacker to potentially reach internal addresses due to improper validation. The issue is fixed in version 3.9.1.