CVE-2026-112375: Apache Kafka · Unauthorized principal can read arbitrary broker files via IncrementalAlterConfigs
Affects kafkaSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.3.2 or 4.2.2 when convenient.
Data as of 17 Nov 2026, 16:49 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 4.3.2, 4.2.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade kafka to 4.3.2 or 4.2.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamikafkapkg:bitnami/kafkaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache Kafka to versions 4.2.2, 4.3.2, or 4.4.0, where authorization checks are enforced before configuration validation and config-provider usage is restricted. Additionally, run Kafka brokers under least-privileged operating system accounts to limit file access and reduce exposure of sensitive data.
Description
An authenticated Kafka principal without authorization can exploit a flaw in IncrementalAlterConfigs or AlterConfigs requests to read arbitrary broker files or environment variables. This occurs because configuration validation happens before authorization checks, allowing resolution of configuration variables that expose sensitive data. The issue affects Kafka versions before 4.2.2 and between 4.3.0 and 4.3.2. The vulnerability is mitigated by upgrading to versions 4.2.2, 4.3.2, or 4.4.0, which enforce authorization before configuration validation and restrict config-provider usage.