$RodHat_/search
MOTD

Apache Kafka's default OAUTHBEARER config silently accepted unsigned JWTs. Upgrading to fix CVE-2026-110985 is not enough.

Published by

This article may contain Amazon affiliate links. I may earn a commission if you buy through them. Disclosure.

Editorial card: Apache Kafka's default OAUTHBEARER config silently accepted unsigned JWTs. Upgrading to fix CVE-2026-110985 is not enough.
Editorial card: RodHat

The alg:none JWT attack is eleven years old. Tim McLean documented it in March 2015: a JWT library that accepts the alg:none header and skips signature verification gives out free admin tokens to anyone who can write JSON. The fix is equally old: reject alg:none at the library level, or better yet fail to start when no verification key is configured. Apache Kafka shipped neither behavior until this week.

CVE-2026-110985 covers SASL/OAUTHBEARER authentication in Kafka 4.1.0 through 4.3.0. When sasl.oauthbearer.jwks.endpoint.url is unset, which is the default, DefaultJwtValidator silently falls back to ClientJwtValidator, a validator that performs no signature checking, no algorithm checking, and no issuer checking. A broker in that state accepts any structurally valid JWT, including tokens carrying "alg":"none". An attacker who can reach the listener sends a hand-crafted token asserting any principal name, including configured superusers, and gets full cluster access. No credentials. No bruteforcing. Just a JSON object.

A companion flaw, CVE-2026-110952, ships in the same defaults: issuer and audience validation are only enforced when administrators explicitly configure them. Brokers using a real signing key may still accept tokens from the wrong issuer if nobody set those fields.

Fixed versions are 4.2.2, 4.3.1, and 4.4.0. Here is the part that will catch people: upgrading is not enough. The patch changes startup behavior. A patched broker now throws a ConfigException and refuses to start if OAUTHBEARER is configured without a verifiable signing key. That means you must set sasl.oauthbearer.jwks.endpoint.url (or configure a custom sasl.oauthbearer.jwt.validator.class) before the upgraded broker will run. Upgrade without updating config: broker is down. Run old config on new version: also down. The migration requires both changes together. Clusters on 4.1.x or older must migrate to a supported branch first; there are no backport patches for those versions.

The batch contains ten other fixes. CVE-2026-114349 is worth separate attention: a roughly 90-byte compressed request triggers a 2 GiB allocation on the broker. Memory exhaustion via a single small packet, no authentication required. CVE-2026-116593 is the bonus round: plaintext configuration values, including credentials, are exposed through a validation REST endpoint. One CVE hands you the cluster. Another hands you everything the cluster uses to authenticate with the rest of your infrastructure.

No confirmed exploitation in the wild as of October 29. That does not mean safe. The CVE-2026-110985 attack path is trivially reproducible from the description, and Kafka clusters typically carry every event stream in an organization. The window between “published” and “weaponized” on authentication bypasses is measured in days.

The recurring shape here is default configurations that work correctly when properly tuned and fail completely when left alone. Last week’s LiteLLM supply chain incident ran on the same failure mode: an OAuth integration that a defender would configure one way and an attacker would reach another. The kernel and security hub has more coverage of this October’s run of authentication and parser-class CVEs, and CVE scoring inflation is relevant context for deciding how seriously to weight a batch that includes both a trivial cluster takeover and a DoS.

Sources

  1. Apache Kafka Fixes 12 Vulnerabilities, Including a JWT Bypass That Grants Full Cluster Access (Security Online)
  2. CVE-2026-110985: Apache Kafka Vulnerability Fix and Details (Strix AI CVE Database)