Skip to main content
No exploitation reported

CVE-2025-66621

Apache James: SASL OAUTHBEARER do not validate aud in JWT payload if misconfigred

No exploitation reported by the sources we read.

  • Published2026-11-06
  • WeaknessCWE-345

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Apache James SASL OAuthBearer/XOAUTH2 prior versions 3.9.1 fails to validate correctly AUD claim of JWT payloads when introspection is not configured. This allows an attacker with valid credentials to access the mail server even if they are not authorized to do so. We recommend users to upgrade to non vulnerable version that forces explicit configuration of aud claims and forces introspection.

Timeline

dates in UTC
  1. 2026-11-0611:38CVE publishedCNA

Versions per branch

Products declared by the CNA

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.

  • Apache Software Foundation Apache Jamesother versions: not affected
    Affected
    • ≥ 3.9.0, < 3.9.1fixed in 3.9.1semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-06

Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2025-66621 yet.

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Published
2026-11-06
Last Modified
2026-11-16
NVD status
Deferred
GitHub Advisory
GHSA-rg6c-rqpp-49q4

Frequently asked questions

What is CVE-2025-66621?

Apache James SASL OAuthBearer/XOAUTH2 prior versions 3.9.1 fails to validate correctly AUD claim of JWT payloads when introspection is not configured. This allows an attacker with valid credentials to access the mail server even if they are not authorized to do so. We recommend users to upgrade to non vulnerable version that forces explicit configuration of aud claims and forces introspection.

Is CVE-2025-66621 actively exploited?

Active exploitation of CVE-2025-66621 has not been confirmed. Its EPSS score was 0.1% on 2026-11-15, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-66621?

CVE-2025-66621 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record