cve.bz

CVE-2026-76171 apache software foundation apache james: SSRF

9.1 criticalEPSS 0.4%

Critical (9.1) in apache software foundation apache james. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
apache (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-76171 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-76171?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-76171?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-76171 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-76171

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-76171](https://cve.bz/cve/badge/CVE-2026-76171.svg)](https://cve.bz/cve/CVE-2026-76171)

HTML:

<a href="https://cve.bz/cve/CVE-2026-76171"><img src="https://cve.bz/cve/badge/CVE-2026-76171.svg" alt="CVE-2026-76171"></a>

Affected

  • apache software foundation:apache james

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Jamesfrom 3.9.0 before 3.9.1

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. Scored 9.1 critical

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON