CVEsApache Software FoundationCVE-2026-112375Published Oct 28, 16:46 · Updated Oct 28, 16:46 UTC
–
Not scored
CVE-2026-112375

Apache Kafka: Unauthorized principal can read arbitrary broker files via IncrementalAlterConfigs

org.apache.kafka:kafka · Missing authorization · CWE-862
Affectedorg.apache.kafka:kafka
FixNo fix listed yet.
PublishedOct 28, 16:46 · apache
ScoredNot yet
Exploit code publicNone known · checked 21:18 UTC
ExploitedNone known · CISA KEV checked 22:11 UTC

What we know

No known exploitation. CISA KEV, checked 22:11 UTC.
No public exploit code known. Exploit-DB, Metasploit, Nuclei, checked 21:18 UTC.
No severity score yet.

Description

An authenticated Kafka principal with no authorization grants (not even ALTER_CONFIGS) can make a broker read a file or an environment variable from the broker host and return its contents. An IncrementalAlterConfigs (or AlterConfigs) request targeting a BROKER resource reaches the broker's configuration validation before any authorization check is applied to that path. Validation resolves configuration variables such as ${file:/path:key} or ${env:VAR} using a ConfigProvider named in the request, and this resolution bypasses the org.apache.kafka.automatic.config.providers allowlist that was added as the mitigation for CVE-2024-31141. An arbitrary ConfigProvider (for example FileConfigProvider or EnvVarConfigProvider) is therefore instantiated and the referenced file or environment variable is read, and a type-validation error returns the resolved content to the caller. Impact: On a cluster with an authorizer enabled, an authenticated principal with no authorization grants can read the contents of files accessible to the broker process, and the broker's environment variables, exposing credentials, keystores, or other secrets, defeating the CVE-2024-31141 allowlist. The read is bounded by the broker process's file permissions. The brokers and the cluster remain available; the issue is disclosure of file and environment- variable contents. Clusters with no authorizer configured are not affected in practice, because every principal already holds ALTER_CONFIGS there. Mitigation: Upgrade to Apache Kafka 4.2.2, 4.3.2, or 4.4.0. As defense in depth, run brokers under a least-privileged operating-system account so that sensitive files are not readable by the broker process. Resolution: From Apache Kafka 4.2.2, 4.3.2, and 4.4.0: broker configuration changes are authorized (ALTER_CONFIGS on the cluster) before the configuration is validated, and configuration- variable resolution enforces the config-providers allowlist.

From apache

Affected and fixed versions

ProductAffectedFixed inorg.apache.kafka:kafka3.2.0 – 4.1.2–org.apache.kafka:kafka4.2.0 – 4.2.1–org.apache.kafka:kafka4.3.0 – 4.3.1–

Exploit code

Exploit-DBnone knownMetasploitnone knownNucleinone known

References

kafka.apache.org/cve-list · kafka.apache.orgvendor advisory

Other CVEs in org.apache.kafka:kafka

All 5 →
–Apache Kafka: Broker OutOfMemoryError via tagged-field allocation amplification in flexible protocol request parsing · CVE-2026-111115Oct 28–Apache Kafka: Broker OutOfMemoryError via array allocation amplification in code-generated protocol readers · CVE-2026-111108Oct 28–Apache Kafka: PushTelemetry (KIP-714) metrics payloads are decompressed without a size limit, allowing a broker out-of-memory denial of service · CVE-2026-111073Oct 28