Skip to main content
CVE-2026-110985VulnerabilityPublished

Apache Kafka: Broker silently skips JWT signature verification for SASL/OAUTHBEARER when the JWKS endpoint URL is not

Affects kafkaSource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-110985· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.3.1 or 4.2.2 as a priority.

Data as of 17 Nov 2026, 16:50 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.19.1
Patch
Available – fixed in 4.3.1, 4.2.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.3.1 or 4.2.2.

Affected software

ProductAffectedFixed in
Bitnamikafkapkg:bitnami/kafkaOther threatsAffected
  • >=4.1.0 <4.2.2
  • >=4.3.0 <4.3.1
Fixed in
  • 4.2.2
  • 4.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Administrators should configure the sasl.oauthbearer.jwks.endpoint.url for every listener and mechanism using OAuthBearerValidatorCallbackHandler to ensure JWT signature verification. Alternatively, configure a signature-verifying sasl.oauthbearer.jwt.validator.class. Upgrading to Apache Kafka versions 4.2.2, 4.3.1, or later will prevent brokers from starting if signature verification is not properly configured, enforcing secure defaults. No upgrade is strictly required if the mitigation is applied correctly.

Description

Apache Kafka brokers using SASL/OAUTHBEARER authentication with the default JWT validator and without a configured JWKS endpoint URL or custom verification key resolver silently skip JWT signature verification. This allows an unauthenticated remote attacker to forge tokens with any principal, including superusers, gaining full cluster access. The issue affects Kafka versions 4.1.0 through before 4.2.2 and 4.3.0 through before 4.3.1. Fixed versions 4.2.2 and 4.3.1 enforce signature verification or fail to start if misconfigured.

References

Community reviews

Loading reviews…