CVE-2026-112375

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

Published Oct 28, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

An Apache Kafka principal that is authenticated but lacking any authorization grants can send an IncrementalAlterConfigs or AlterConfigs request targeting a BROKER resource. The broker processes the configuration validation before performing the authorization check, and during this phase it resolves configuration variables that reference files or environment variables using the ConfigProvider specified in the request. Because this resolution occurs before the newly added allowlist enforcement for config providers, the arbitrarily specified provider (e.g., FileConfigProvider or EnvVarConfigProvider) is instantiated and the target file or environment variable is read. A validation error then returns the resolved content back to the caller, allowing the principal to read broker‑host files or environment variables. The vulnerability is a CWE‑862 and CWE‑209 defect, indicating missing authorization checks for privileged operations and exposing arbitrary files or environment variables.

Affected Systems

The flaw exists in all released versions of Apache Kafka prior to the security updates included in 4.2.2, 4.3.2, and 4.4.0. The affected environment is a Kafka cluster that has an authorizer enabled; with an authorizer, a principal that has no ALTER_CONFIGS or other grant can exploit the vulnerability. Clusters running without an authorizer are effectively not impacted because such principals effectively hold ALTER_CONFIGS by default.

Risk and Exploitability

Because the vulnerability only discloses data and does not compromise the broker’s availability or integrity, its severity in terms of CVSS is 6.5. However, any authenticated principal that can read arbitrary files or environment variables can expose sensitive credentials or keys, leading to credential compromise. The EPSS score is < 1%, and the flaw is not listed in CISA’s KEV catalog. The likely attack vector is an internal user or compromised service that is authenticated against the broker but has no explicit authorization grants. Exploitation requires that the attacker be able to dispatch a configuration change request, which is typically trivial for a normal user in a Kafka environment that relies on authorizers to enforce permissions. The missing authorization (CWE‑862) and the ability to read sensitive data (CWE‑209) both contribute to the risk assessment.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Apache Kafka 4.2.2, 4.3.2, or 4.4.0 to ensure that configuration changes are authorized before validation and that the allowlist for config providers is enforced.
  • Run broker processes under a least‑privileged operating‑system account so that even if a file or environment variable is read, it is limited to the broker’s accessible file space.
  • Verify that the broker’s configuration provider allowlist is active by attempting a test configuration resolution after the upgrade to confirm the provider restriction is functioning as intended.

Generated by OpenCVE AI on November 6, 2026 at 01:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

Type Values Removed Values Added
First Time appeared Apache
Apache kafka
Vendors & Products Apache
Apache kafka
Type Values Removed Values Added
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.
Title Apache Kafka: Unauthorized principal can read arbitrary broker files via IncrementalAlterConfigs
Weaknesses CWE-862
References
Weaknesses
  • CWE-209

    Generation of Error Message Containing Sensitive Information

  • CWE-862

    Missing Authorization

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 5, 2026, 5:26 PM
Reserved
Oct 19, 2026, 4:21 PM
Status
Awaiting Analysis
Published
Oct 28, 2026, 5:17 PM
Modified
Nov 5, 2026, 6:17 PM
Severity
Moderate
Public date
Oct 28, 2026, 4:46 PM