# CVE-2026-112375: Apache Kafka: Unauthorized principal can read arbitrary broker files via IncrementalAlterConfigs


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-pvjw-82p3-hmj7, UBUNTU-CVE-2026-112375

## What is CVE-2026-112375?

CVE-2026-112375 is a vulnerability in Apache Kafka, published on 28 Oct 2026. 

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-112375?


## How do I fix CVE-2026-112375?

No fix has been published for CVE-2026-112375 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112375 being exploited?

There is no known exploitation of CVE-2026-112375 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112375 and fix it if it is affected.

What it is: CVE-2026-112375 is a vulnerability in Apache Kafka, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112375 in the wild and no public exploit code.

Affected product: Apache Kafka. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112375/ (Markdown: https://insights.sbomify.com/CVE-2026-112375/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112375
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112375
- OSV: https://osv.dev/vulnerability/CVE-2026-112375

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112375/
Summaries are generated and may contain mistakes; the official description above is the record.