Apache James: SASL OAUTHBEARER do not validate aud in JWT payload if misconfigured (CVE-2025-66621)
SASL OAuthBearer fails to validate AUD claim in JWT payload when not configured.
8 stories, newest first · one card per story
SASL OAuthBearer fails to validate AUD claim in JWT payload when not configured.
Affects 3.8.0-3.9.6; client-supplied authzid bypasses SASL checks
jabberd2 allows SASL ANONYMOUS authentication even when disabled in configuration.
Apache calls the flaw important: peers can send regular AMQP frames that Proton dispatches as SASL, with no username set.
DefaultJwtValidator verifies signatures only if sasl.oauthbearer.jwks.endpoint.url is set; that setting is unset by default.
Apache rates the flaw important across Tomcat 7 through 11 ranges when JNDIRealm uses non-GSSAPI SASL.
Publicly reported Cyrus SASL security issues remain unfixed, with no maintainer response and no release since 2022.
Authen::SASL::Perl::DIGEST_MD5 before 2.2100 for Perl accepts replayed DIGEST-MD5 authentication responses via unverified nonce handling (CVE-2026-86219).
Today 1.5K readers · 2.4K views · 754 reads · all time 189K views