- Exploited
- No known exploitation
- Fix
- Fixed in 3.9.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.9.1.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 1/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache James server, through the JMAP PushSubscription web-push client, has an SSRF filter bypass that lets an attacker reach internal network addresses. Because no attacker access details or advisory impact are given, the way the flaw is reached is not stated.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity1/10Rated low by apache
- No patch0/5No signal
What would change the score
- Would score about 56 if added to CISA KEV
- Would score about 51 if CISA's SSVC rates exploitation active
- Would score about 23 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.9.1.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Apache Software Foundation Apache James
From 3.9.0 · fixed in 3.9.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-76171
Is CVE-2026-76171 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-76171?
Apache James: from 3.9.0 before 3.9.1.Source: cve.now feed data
How do I fix CVE-2026-76171?
Upgrade to a fixed version: 3.9.1.Source: cve.now feed data