In Apache James server prior version 3.9.1 improper validation in JMAP webPush SSRF validation did lead to the
Source GCVE Database
Not known to be exploited : upgrade to 3.9.1 soon.
Data as of 6 Nov 2026, 13:23 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
|
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 should upgrade to Apache James server version 3.9.1, which contains the fix for this SSRF validation vulnerability. No other mitigation steps are indicated.
Description
Apache James server versions prior to 3.9.1 contain an improper validation vulnerability in the JMAP webPush SSRF functionality that allows reaching internal addresses. This issue is fixed in version 3.9.1.