Apache Kafka: Broker does not enforce JWT issuer and audience validation for SASL/OAUTHBEARER by default
Affects kafkaSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 5.9 Medium : upgrade to 4.4.0 when convenient.
Data as of 17 Nov 2026, 16:50 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 4.4.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Upgrade kafka to 4.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamikafkapkg:bitnami/kafkaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
For all affected versions (>=3.1.0 <4.4.0), set the configuration options sasl.oauthbearer.expected.issuer to the exact issuer value and sasl.oauthbearer.expected.audience to the expected audience(s) per listener. This enforces exact-match checks on issuer and audience claims and mitigates the vulnerability. From version 4.4.0 onward, these settings are mandatory for brokers configured with a JWKS endpoint, and the broker will fail to start if they are not set. Deployments that intentionally do not restrict issuer or audience can opt out using sasl.oauthbearer.allow.unverified.issuer=true and/or sasl.oauthbearer.allow.unverified.audience=true.
Description
Apache Kafka brokers using SASL/OAUTHBEARER with the bundled JWKS-backed validator do not enforce JWT issuer and audience validation by default prior to version 4.4.0. This means that unless explicitly configured, tokens signed by any issuer or lacking an audience claim may be accepted if their signature is valid. From version 4.4.0, brokers require explicit configuration of issuer and audience validation or can opt out with specific flags.