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