Quick answers
- Is CVE-2025-66621 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-66621 being exploited in the wild.
- How severe is CVE-2025-66621?
- 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-2025-66621?
- 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-2025-66621 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2025-66621?
- 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
The vulnerability exists in SASL OAuthBearer and XOAUTH2 authentication handlers in Apache James prior to version 3.9.1, which do not correctly validate the AUD (audience) claim of JWT payloads when token introspection is disabled. An attacker with valid OAuth credentials can exploit this to gain unauthorized access to the mail server by presenting a token with a missing or incorrect audience claim that should have been rejected.
Affected products
- Apache James prior to 3.9.1
Timeline
- 2026-11-06: disclosed