Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.1
CVE-2026-110985: Apache Kafka brokers accept forged tokens without JWKS URL
CVE-2026-110985 · published 2 days ago
Summary
Kafka brokers that use the SASL/OAUTHBEARER login method but do not configure a JWKS endpoint URL will not check the digital signature on the token they receive. This lets anyone who can reach the broker send a fake token and appear as any user, even a super‑user, gaining full control of the cluster. To protect yourself, configure a JWKS endpoint URL (or a custom validator that verifies signatures) for every listener that uses OAuthBearer validation.
What to do
- Update kafka to version 4.3.1.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | apache software foundation | apache kafka | <= 4.1.2 |
| Ubuntu:Pro:18.04:LTS | canonical | kafka | All versions |
| Bitnami | – | kafka |
>= 4.3.0, < 4.3.1 Fix: upgrade to 4.3.1
|
Original advisory text
Apache Kafka: Broker silently skips JWT signature verification for SASL/OAUTHBEARER when the JWKS endpoint URL is not configured
A Kafka broker using SASL/OAUTHBEARER with the default validator (sasl.oauthbearer.jwt.validator.class=DefaultJwtValidator) selects its implementation from configuration. When sasl.oauthbearer.jwks.endpoint.url is set, the validator verifies the JWT signature. When that URL is unset (the default) and no verification key resolver is supplied, DefaultJwtValidator silently falls back to ClientJwtValidator, which does not verify the JWT signature, algorithm, or issuer - and the broker starts with no warning or error. This is the residual of CVE-2026-33557, whose fix restored signature verification only on the path where the JWKS endpoint URL is set.
Impact:
A broker in this state accepts any structurally valid JWT, including "alg":"none" tokens. An unauthenticated remote attacker who can reach the listener can forge a token asserting any principal - including configured superusers - and gain full access to the cluster. Only brokers that enable SASL/OAUTHBEARER validation without a JWKS endpoint URL (and without a custom verification key resolver) are affected; brokers that set the URL verify signatures and are not affected. Unlike CVE-2026-110952 (issuer/audience not enforced by default), here no signature is verified at all.
Mitigation (all affected versions, no upgrade required):
Set sasl.oauthbearer.jwks.endpoint.url for every listener/mechanism that uses OAuthBearerValidatorCallbackHandler, or configure a signature-verifying sasl.oauthbearer.jwt.validator.class.
Resolution:
From Apache Kafka 4.2.2, 4.3.1, and 4.4.0: a broker that would fall back to the non-verifying ClientJwtValidator fails to start with a ConfigException instead of running without signature verification (secure by default).
Impact:
A broker in this state accepts any structurally valid JWT, including "alg":"none" tokens. An unauthenticated remote attacker who can reach the listener can forge a token asserting any principal - including configured superusers - and gain full access to the cluster. Only brokers that enable SASL/OAUTHBEARER validation without a JWKS endpoint URL (and without a custom verification key resolver) are affected; brokers that set the URL verify signatures and are not affected. Unlike CVE-2026-110952 (issuer/audience not enforced by default), here no signature is verified at all.
Mitigation (all affected versions, no upgrade required):
Set sasl.oauthbearer.jwks.endpoint.url for every listener/mechanism that uses OAuthBearerValidatorCallbackHandler, or configure a signature-verifying sasl.oauthbearer.jwt.validator.class.
Resolution:
From Apache Kafka 4.2.2, 4.3.1, and 4.4.0: a broker that would fall back to the non-verifying ClientJwtValidator fails to start with a ConfigException instead of running without signature verification (secure by default).
References
- https://kafka.apache.org/cve-list URL
- https://ubuntu.com/security/CVE-2026-110985 Third Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-110985 Third Party Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-110985 URL
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker full control
Severity
9.1
Critical
Type
CWE-345Insufficient Verification of Data Authenticity
CWE-347Improper Verification of Cryptographic Signature
CWE-636Not Failing Securely ('Failing Open')
CWE-1287Improper Validation of Specified Type of Input
Timeline
Published17 Nov 2026
Updated17 Nov 2026
First seen28 Oct 2026
Sources
CVE-2026-110985 · NVD
CVE-2026-110985 · MITRE
UBUNTU-CVE-2026-110985 · OSV
BIT-kafka-2026-110985 · OSV
Track software like this
Free during beta