CVE-2026-112375VulnerabilityPublished 28 Oct 2026

An authenticated Kafka principal with no authorization grants (not even ALTER_CONFIGS) can make a broker read a file

Source GCVE Database

Mentioned vulnerabilities

CVE-2024-31141

Authoritative record:CVE-2026-112375· High

Not known to be exploited · fixed in 4.2.2 : patch Apache Kafka soon.

Data as of 28 Oct 2026, 19:57 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in 4.2.2

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-pvjw-82p3-hmj7

What to do

Affected software

Product	Affected	Fixed in
Apache Kafkaorg.apache.kafka:kafka	Affected >=3.2.0 <=4.1.2 >=4.2.0 <=4.2.1 >=4.3.0 <=4.3.1	Fixed in–
MavenApache Software Foundation/org.apache.kafka:kafka`pkg:maven/Apache Software Foundation/org.apache.kafka:kafka`Other threats	Affected >=3.2.0 <=4.1.2 >=4.2.0 <=4.2.1 >=4.3.0 <=4.3.1	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 is enforced before configuration validation and config-provider resolution is restricted. Additionally, run Kafka brokers under least-privileged operating system accounts to limit file access and protect sensitive files from being read by the broker process.

Description

An authenticated Kafka principal without any authorization grants can exploit a flaw in broker configuration validation to read files or environment variables from the broker host. This occurs because configuration validation resolves variables before authorization checks, bypassing existing allowlists. The vulnerability allows disclosure of sensitive broker-hosted files and environment variables, potentially exposing secrets. The issue is fixed in Apache Kafka versions 4.2.2, 4.3.2, and 4.4.0 by enforcing authorization before validation and restricting config-provider usage.

Impact

An authenticated Kafka principal without any authorization grants can read files and environment variables accessible to the broker process, potentially exposing sensitive information such as credentials and keystores. The disclosure is limited by the broker process's file permissions. The brokers and cluster remain operational; the vulnerability results in information disclosure only. Clusters without an authorizer configured are not practically affected since all principals have ALTER_CONFIGS rights there.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 19:57 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats