BIT-kafka-2026-110985

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/kafka/BIT-kafka-2026-110985.json
JSON Data
https://api.osv.dev/v1/vulns/BIT-kafka-2026-110985
Aliases
  • CVE-2026-110985
Published
2026-11-17T11:47:13Z
Modified
2026-11-17T13:30:09Z
Summary
Apache Kafka: Broker silently skips JWT signature verification for SASL/OAUTHBEARER when the JWKS endpoint URL is not configured
Details

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).

Database specific
{
    "cpes":  [
        "cpe:2.3:a:apache:kafka:*:*:*:*:*:maven:*:*"
    ],
    "severity":  "Critical"
}
References

Affected packages

Bitnami / kafka

Package

Name
kafka
Purl
pkg:bitnami/kafka

Severity

  • 9.1 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
4.1.0
Fixed
4.2.2
Introduced
4.3.0
Fixed
4.3.1

Database specific

source
"https://github.com/bitnami/vulndb/tree/main/data/kafka/BIT-kafka-2026-110985.json"