Skip to main content
Mallory
Medium

Improper Authorization in Apache Kafka CONSUMER_GROUP_DESCRIBE API

IdentifiersCVE-2026-41115CWE-285· Improper Authorization

CVE-2026-41115 is an improper authorization issue in Apache Kafka affecting versions 4.0.0 through 4.3.0. The issue concerns the CONSUMER_GROUP_DESCRIBE (API key 69) authorization model. Kafka documentation and KIP-848 documented READ on the GROUP resource as the required permission, while the implementation actually validates DESCRIBE on the GROUP resource. This discrepancy can cause administrators to configure ACLs incorrectly based on the published documentation, producing unintended authorization outcomes. Apache states that the implementation is correct and that the documentation and KIP-848 will be updated to reflect that the proper permission for CONSUMER_GROUP_DESCRIBE is DESCRIBE GROUP.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

The primary impact is unintended access control behavior caused by ACL misconfiguration. Environments that followed the incorrect documented permission model may grant READ permission to principals that should not be able to join or sync consumer groups, or may allow principals with DESCRIBE permission but without READ permission to access sensitive consumer group metadata. This can expose group metadata and create an authorization posture that violates least-privilege expectations.

Mitigation

If you can’t patch tonight, do this now.

Audit existing group ACLs in Kafka deployments for any rules created from the incorrect assumption that CONSUMER_GROUP_DESCRIBE requires READ. Apply least-privilege principles by granting only DESCRIBE on the GROUP resource where metadata visibility is intended, and avoid overbroad READ grants that could enable unintended group interaction capabilities. Validate authorization behavior in staging before rollout if ACLs are centrally managed or templated.

Remediation

Patch, then assume compromise.

Review and correct Apache Kafka ACLs for consumer group operations so that CONSUMER_GROUP_DESCRIBE is governed by DESCRIBE on the GROUP resource, not READ. Update operational runbooks, internal documentation, and any automation or policy templates derived from the prior Kafka documentation or KIP-848. Track and adopt the upstream documentation updates from Apache Kafka reflecting the corrected permission requirement.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationKafkaapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.