# CVE-2026-76171: Apache James server JMAP webPush SSRF validation bypass

Source: https://junglewise.ai/threats/cve-2026-76171-in-apache-james-server-prior-version-3-9-1-improper-validation-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-06. Updated: 2026-11-06  
License: CC BY 4.0 with a link back

CVE-2026-76171 · Severity: info · Published 2026-11-06

Apache James is an email and messaging server used by organizations to manage internal communications. A vulnerability in its JMAP webPush feature allows attackers to bypass security checks and reach internal network addresses that should be restricted, potentially exposing sensitive internal systems.

Technologies: [Apache James](https://junglewise.ai/threats/technologies/james). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-76171 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-76171 being exploited in the wild.

**How severe is CVE-2026-76171?** Informational severity, published 6 November 2026.

**Which products and versions are affected?** Apache James prior to 3.9.1.

**Is there a fix for CVE-2026-76171?** Yes: fixed in 3.9.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-76171 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-76171?** Check whether you run Apache James at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 3.9.1

## Technical details

An improper validation flaw in the JMAP webPush SSRF protection in Apache James prior to 3.9.1 allows attackers to reach internal addresses by circumventing the intended security controls. The vulnerability permits Server-Side Request Forgery (SSRF) attacks against internal network resources. The flaw is resolved in version 3.9.1.

## Affected products

- Apache James prior to 3.9.1

## Timeline

- 2026-11-06: disclosed

## References

- [https://lists.apache.org/thread.html/goj9xc05nbk1dp0z2g3r264j537lvx9r](https://lists.apache.org/thread.html/goj9xc05nbk1dp0z2g3r264j537lvx9r)

## Related threats

- [Apache James Mime4J resource exhaustion in MIME parsing](https://junglewise.ai/threats/cve-2026-85111-allocation-of-resources-without-limits-or-throttling-in-apache)
- [Apache James path traversal in SieveFileRepository](https://junglewise.ai/threats/cve-2026-76168-in-apache-james-server-prior-version-3-9-1-relying-on-the)
- [Apache James ACL bypass in JMAP protocol](https://junglewise.ai/threats/cve-2026-49939-in-apache-james-server-prior-version-3-9-1-improper-access)
- [Apache James SASL OAuthBearer/XOAUTH2 AUD claim validation bypass](https://junglewise.ai/threats/cve-2025-66621-apache-james-sasl-oauthbearer-xoauth2-prior-versions-3-9-1-fails)