Skip to main content
VulnerabilityPublished

CVE-2025-66621: Apache James · Insufficient Verification of Data Authenticity

Affects Apache JamesSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 3.9.1 soon.

Data as of 6 Nov 2026, 12:03 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
Patch
Available – fixed in 3.9.1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Apache James to 3.9.1.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache JamesAffected
  • >=3.9.0 <3.9.1
Fixed in
  • 3.9.1

AI-suggested

Upgrade Apache James to version 3.9.1 or later, which includes a fix that enforces explicit configuration of AUD claims and requires introspection. No other mitigation is indicated.

Description

Apache James versions prior to 3.9.1 contain a vulnerability in SASL OAuthBearer/XOAUTH2 authentication where the AUD claim in JWT payloads is not properly validated if introspection is not configured. This flaw allows attackers with valid credentials to gain unauthorized access to the mail server. The issue is resolved in version 3.9.1, which requires explicit configuration of AUD claims and enforces introspection.

References

Community reviews

Loading reviews…