CVE-2026-33557: Apache Kafka: Missing JWT token validation in OAUTHBEARER authentication

Published Apr 17, 2026
·
Updated

A possible security vulnerability has been identified in Apache Kafka.

By default, the broker property sasl.oauthbearer.jwt.validator.class is set to org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator. It accepts any JWT token without validating its signature, issuer, or audience. An attacker can generate a JWT token from any issuer with the preferredusername set to any user, and the broker will accept it.

We advise the Kafka users using kafka v4.1.0 or v4.1.1 to set the config sasl.oauthbearer.jwt.validator.class to org.apache.kafka.common.security.oauthbearer.BrokerJwtValidator explicitly to avoid this vulnerability. Since Kafka v4.1.2 and v4.2.0 and later, the issue is fixed and will correctly validate the JWT token.

Affected Software

2 affected components
Apache Kafka>=4.1.0<=4.1.1
Apache Kafka>=4.1.0<4.1.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache Kafka to a version that resolves this vulnerability.

    Fixed in 4.1.2
  2. Upgrade

    Upgrade Apache Kafka to a version that resolves this vulnerability.

    Fixed in 4.2.0
  3. Configuration

    On Kafka versions v4.1.0 or v4.1.1, explicitly set sasl.oauthbearer.jwt.validator.class to org.apache.kafka.common.security.oauthbearer.BrokerJwtValidator to ensure JWT token validation (signature, issuer, and audience) instead of accepting any JWT token.

    Apache Kafka broker (OAUTHBEARER) sasl.oauthbearer.jwt.validator.class = org.apache.kafka.common.security.oauthbearer.BrokerJwtValidator

Event History

Apr 20, 2026
CVE Published
via MITRE·01:28 PM
Data Sourced
via MITRE·01:28 PM
DescriptionWeakness
Data Sourced
via Red Hat·02:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-33557?

CVE-2026-33557 is considered a high-severity vulnerability due to improper JWT token validation in OAUTHBEARER authentication.

2

How do I fix CVE-2026-33557?

To fix CVE-2026-33557, update Apache Kafka to version 4.1.2 or later, which addresses the missing JWT token validation.

3

What are the risks associated with CVE-2026-33557?

CVE-2026-33557 can allow unauthenticated users to gain access by bypassing the token validation, potentially exposing sensitive data.

4

Which versions of Apache Kafka are affected by CVE-2026-33557?

CVE-2026-33557 affects Apache Kafka versions 4.1.0 to 4.1.1.

5

Is there a workaround for CVE-2026-33557?

For CVE-2026-33557, configuring a custom JWT validator may serve as a temporary workaround until the software is updated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203