CVE-2024-27309 | Apache Kafka: Potential incorrect access control during migration from ZK mode to KRaft mode

While an Apache Kafka cluster is being migrated from ZooKeeper mode to KRaft mode, in some cases ACLs will not be correctly enforced. Two preconditions are needed to trigger the bug: 1. The administrator decides to remove an ACL 2. The resource associated with the removed ACL continues to have two or more other ACLs associated with it after the removal. When those two preconditions are met, Kafka will treat the resource as if it had only one ACL associated with it after the removal, rather than the two or more that would be correct. The incorrect condition is cleared by removing all brokers in ZK mode, or by adding a new ACL to the affected resource. Once the migration is completed, there is no metadata loss (the ACLs all remain). The full impact depends on the ACLs in use. If only ALLOW ACLs were configured during the migration, the impact would be limited to availability impact. if DENY ACLs were configured, the impact could include confidentiality and integrity impact depending on the ACLs configured, as the DENY ACLs might be ignored due to this vulnerability during the migration period.

Published: 2024-04-12 Last update: 2025-06-10 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-27309 is rated Moderate Risk (51.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.11%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-27309

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.39% 1.11% +0.73%
2 2026-01-24 0.29% 0.39% +0.10%
3 2025-11-21 0.29%

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-27309

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.4 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
2.2 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-27309

GitHub Security Advisory for CVE-2024-27309

GHSA-79vv-vp32-gpp7 · Severity: high · Ecosystem: maven — Apache Kafka: Potential incorrect access control during migration from ZK mode to KRaft mode

OS Trackers for CVE-2024-27309

vendor priority summary link
redhat medium https://access.redhat.com/security/cve/CVE-2024-27309
suse medium https://www.suse.com/security/cve/CVE-2024-27309/
ubuntu medium CVE-2024-27309 medium priority: Ubuntu including 1 source packages (kafka), 8 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream): DNE 6, needs-triage 2. https://ubuntu.com/security/CVE-2024-27309

Affected software / configurations for CVE-2024-27309

Vendor Product Version Raw CPE
apache kafka >= 3.5.0, <= 3.6.1 cpe:2.3:a:apache:kafka:*:*:*:*:*:*:*:*

References for CVE-2024-27309

cvelogic Threat Intelligence