Skip to main content

Apache James CVE-2026-76171

| EUVDEUVD-2026-118217 CRITICAL
Server-Side Request Forgery (SSRF) (CWE-918)
2026-11-06 apache GHSA-qr8x-486x-7mhg
9.1
CVSS 3.1 · Vendor: apache
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to JMAP mailbox
  2. Delivery
    Create webPush subscription with internal URL
  3. Exploit
    Bypass SSRF address validation
  4. Execution
    Server issues request to internal host
  5. Impact
    Reach internal services / exfil or recon

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a JMAP-enabled Apache James deployment (prior to 3.9.1) and an authenticated account able to create a webPush subscription; the attacker supplies a subscription notification URL and the server's internal-address SSRF validation fails to reject it, causing James to reach internal addresses. Limiting factors: JMAP and its webPush subscription feature must be enabled, and a valid authenticated session is needed, so this is not exploitable pre-authentication against a default minimal setup; the degree of data return (full vs. blind SSRF) is not described in the available sources. The only complete fix per the Apache advisory is upgrading to 3.9.1.

Impact

Risk signals are sparse but consistent toward a moderate, non-urgent priority. The input provides NO CVSS score or vector, NO EPSS probability, and NO KEV listing, and the only reference is the Apache advisory itself (no public exploit identified at time of analysis). The vuln.today Decision label is 'monitor', the lowest-urgency tier, aligning with the absence of exploitation evidence. The vulnerability is a CWE-918 SSRF in the JMAP webPush subscription validation of Apache James: the server-side check meant to block internal addresses can be bypassed, letting a user cause the server to reach internal network addresses. Because creating a webPush subscription via JMAP requires an authenticated mailbox session, this is realistically an authenticated-user capability rather than a pre-auth internet-facing flaw - but note that authentication requirements are not confirmed from a CVSS vector (none was provided) and are inferred from how JMAP webPush works; verify against the Apache advisory. Real-world impact is bounded: SSRF to internal addresses can enable internal reconnaissance or pivoting, but the description does not state that response contents are returned to the attacker, so it may be partially or fully blind. Net: a legitimate issue worth patching on a normal cycle, not a high-CVSS/low-risk mirage and not an emergency given 'monitor' status and no exploitation data.

Exploit ScenarioDerived

An authenticated James user with JMAP access registers a webPush subscription whose notification URL points at an internal-only host (e.g., a cloud metadata endpoint or an internal admin service). The server's SSRF validation fails to reject the internal target, so James issues outbound requests from inside the trust boundary, enabling internal reconnaissance or interaction with services not otherwise reachable. No public exploit identified at time of analysis; the trigger beyond 'improper validation in JMAP webPush SSRF validation' is not detailed in the available sources.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 06, 2026

Server-side request forgery in Apache James server (all versions prior to 3.9.1) lets an authenticated JMAP user reach internal addresses through the webPush subscription feature, because the validation intended to reject internal notification URLs is improperly implemented. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N: exploitation requires a JMAP-enabled deployment and a valid account able to create a webPush subscription, so it is not reachable pre-authentication against a minimal default setup, and the scope change reflects that the impact extends beyond the James process into the internal network. No public exploit code has been identified, the issue is not in CISA KEV, and the vendor's only complete fix is upgrading to 3.9.1.

RemediationAI

Upgrade Apache James server to 3.9.1, which the Apache advisory describes as the fix for this issue and the only complete remediation; the advisory is at https://lists.apache.org/thread.html/goj9xc05nbk1dp0z2g3r264j537lvx9r. Until the upgrade is applied, the practical compensating controls follow from the assessed preconditions: disable or do not expose JMAP if it is not required (trade-off: clients depending on JMAP lose mail, contacts and calendar access), and where JMAP must remain available, restrict webPush subscription creation or gate it to trusted accounts (trade-off: legitimate push notifications stop working or are limited to a subset of users). Because the defect is an egress-side validation failure, constraining outbound network access from the James hosts so that loopback-, link-local- and private-range destinations are not reachable limits what a bypassing subscription URL can touch (trade-off: James may lose access to legitimate internal services such as an internal directory, database or mail store that share the restricted ranges). These measures reduce exposure only; per the vendor, updating to 3.9.1 remains the only complete fix.

Affected VersionsENISA

Apache James 3.9.0 <3.9.1

Affected Packages

euvd apache_james fix: 3.9.1

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

JMAP is the JSON-based mail, contacts and calendar protocol served by Apache James, and its webPush extension lets a client register a notification URL that the mail server itself calls when new data arrives. That server-initiated callback makes the subscription URL a classic CWE-918 server-side request forgery sink: the URL supplied by the client is fetched by the server, so any failure to properly validate it allows the James process to be pointed at loopback, link-local, private-range or otherwise internal endpoints reachable from the server's network position. The flaw here is specifically improper validation inside the JMAP webPush SSRF check, meaning the intended internal-address rejection is not effective; the available sources do not describe which address ranges or URL forms bypass the check, nor whether the response data is returned to the attacker or the request is blind. The assessed scope-changed rating with low confidentiality impact is consistent with an internal-reachability primitive whose data-return characteristics are unconfirmed.

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

Vendor (apache) PRIMARY 9.1 LOW
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 5.0 MEDIUM

Authenticated JMAP user needed (PR:L) over the network (AV:N/AC:L); reaching internal hosts crosses a trust boundary (S:C) with limited, possibly blind confidentiality impact (C:L).

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

2
CVSS changed
Nov 10, 2026 - 19:38 NVD
9.1 (CRITICAL)
Patch available
Nov 06, 2026 - 13:17 EUVD

DescriptionCVE.org

In Apache James server prior version 3.9.1 improper validation in JMAP webPush SSRF validation did lead to the possibility to reach internal addresses. Users are recommended to upgrade to version 3.9.1 which fixes this issue.

Threat Intelligence Overview

EPSS Score
0.2%
Top 88% exploitable
Prevalence
Low
Java/JMAP mail server with modest, niche deployment versus mainstream mail platforms
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

20
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +20
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy