Security Digest · Vulnerability record

CVE-2026-33557: Apache Kafka does not validate JWT tokens in its OAUTHBEARER authentication implementation

A possible security vulnerability has been identified in Apache Kafka.

CVSS 8.6 High EPSS 0.9% · p60

Should you act?

Normal patch cycle

No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.9%, percentile 60: FIRST’s model estimates a 0.9% chance of exploitation activity in the next 30 days, higher than 60% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes org.apache.kafka:kafka-clients (Maven) >= 4.1.0, < 4.1.2, fixed in 4.1.2. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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

Apache advises 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.

Weakness type: CWE-1285, CWE-303.

Product: org.apache.kafka:kafka-clients (Maven) · Assigned by: apache · Published: 2026-04-20

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
Mavenorg.apache.kafka:kafka-clients>= 4.1.0, < 4.1.24.1.2
VendorProductAffected versions (per CVE record)
Apache Software FoundationApache Kafka4.1.0 <= 4.1.1

Severity scores

Scored byCVSSScoreVector
CISA-ADP3.19.1 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
redhat-SADP3.18.6 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
GitHub3.19.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable yes, technical impact partial.
  • FIRST EPSS (model of 2026-10-21): 0.93% probability of exploitation activity in the next 30 days; percentile 60.

Timeline

  • — CVE record published by apache
  • — GitHub-reviewed advisory GHSA-28jg-cgg7-j4wc published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

  1. kafka.apache.org kafka.apache.org

Vulnerability records

  1. GitHub Advisory GHSA-28jg-cgg7-j4wc github.com
  2. CVE.org record CVE-2026-33557 cve.org
  3. NVD entry CVE-2026-33557 nvd.nist.gov

Other references from the CVE record and advisory

  1. lists.apache.org lists.apache.org
  2. openwall.com openwall.com
  3. access.redhat.com access.redhat.com
  4. RHBZ#2459739 bugzilla.redhat.com
  5. security.access.redhat.com security.access.redhat.com
  6. github.com github.com

Critical Maven advisories · Today’s Security Digest