cve.bz

CVE-2026-110985 apache software foundation apache kafka: Failing Open

9.1 criticalEPSS 0.2%

Critical (9.1) in apache software foundation apache kafka. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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).

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-345 Insufficient Verification of Data Authenticity
CWE-347 Improper Verification of Cryptographic Signature
CWE-636 Not Failing Securely (Failing Open)
CWE-1287 Improper Validation of Specified Type of Input
OWASP Top 10
A04:2025 Cryptographic Failures, A08:2025 Software or Data Integrity Failures, A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-110985 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110985?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110985?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110985 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • apache software foundation:apache kafka

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Kafkafrom 4.1.0 through 4.1.2
Apache Software Foundation Apache Kafkafrom 4.2.0 through 4.2.1
Apache Software Foundation Apache Kafka4.3.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
UbuntuPro:18.04:LTSkafkano fix listedUBUNTU-CVE-2026-110985

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because an unauthenticated attacker who can reach a Kafka broker listener configured for SASL/OAUTHBEARER without a JWKS endpoint or custom key resolver can forge a JWT and impersonate any principal, including superusers.

Red Hat products are not affected by this flaw. The issue is limited to the Apache Kafka broker's default JWT validator path. Offerings that ship only kafka-clients libraries or use Kafka solely as a producer or consumer (including OpenShift Serverless kn-ekb components) do not perform this broker-side token acceptance. AMQ Streams versions matched for this flaw ship Kafka 4.0.x, which is outside the upstream affected range (4.1.0 and later). Deployments using other SASL mechanisms or mTLS-only authentication are also not impacted.

Red Hat's mitigation

Red Hat is not aware of any available mitigation for this issue. Customers are advised to apply the relevant security updates as they become available.

ProductPackageStateAdvisory
OpenShift Serverlessopenshift-serverless-1/kn-ekb-dispatcher-rhel9Not affected
OpenShift Serverlessopenshift-serverless-1/kn-ekb-receiver-rhel9Not affected
Red Hat build of Apache Camel 4 for Quarkus 3kafka-clientsNot affected
Red Hat build of Apache Camel for Spring Boot 4kafka-clientsNot affected
Red Hat build of Apicurio Registry 3kafka-clientsNot affected
Red Hat build of Debezium 3kafka-clientsNot affected
Red Hat build of Quarkuskafka-clientsNot affected
Red Hat Fuse 7kafka-clientsNot affected
streams for Apache Kafka 3kafka-clientsNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-110985.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON