# CVE-2026-24308: Apache ZooKeeper: Sensitive information disclosure in client configuration handling > Attackers can expose sensitive client configuration data in ZooKeeper logs due to improper handling of configuration values. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Mar 2026 - **Updated:** 15 Jul 2026 - **Also known as:** BIT-zookeeper-2026-24308, CLEANSTART-2026-JW75132, CLEANSTART-2026-LF42316, DEBIAN-CVE-2026-24308, ECHO-3f43-4964-01f0, GHSA-crhr-qqj8-rpxc, MINI-2vfg-c32h-m3q9, MINI-2xf4-223p-78qg, MINI-35gm-pcpx-3chv, MINI-47w7-8759-9wfg, MINI-72f5-3277-8qqr, MINI-cc86-pj9r-766m, MINI-cr9x-jjff-hwxm, MINI-cv26-2h63-j3m4, MINI-ffgg-prqp-c3qq, MINI-hp9p-h5gm-2x4j, MINI-hwhf-g5cp-295g, MINI-j5xj-3mf8-pj33, MINI-mv94-rwvc-2mhx, MINI-qchh-2hh3-f782, MINI-w8vw-qwvm-q2cf, MINI-wf4j-xwj8-p8qh, MINI-xjxf-w6x9-7xwh, ROOT-APP-MAVEN-CVE-2026-24308, UBUNTU-CVE-2026-24308 ## What is CVE-2026-24308? CVE-2026-24308 is a medium-severity vulnerability in Apache ZooKeeper, published on 7 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Improper handling of configuration values in ZKConfig in Apache ZooKeeper 3.8.5 and 3.9.4 on all platforms allows an attacker to expose sensitive information stored in client configuration in the client's logfile. Configuration values are exposed at INFO level logging rendering potential production systems affected by the issue. Users are recommended to upgrade to version 3.8.6 or 3.9.5 which fixes this issue. Weakness: CWE-117 (Improper Output Neutralization for Logs), CWE-532 (Insertion of Sensitive Information into Log File) ## Which versions are affected by CVE-2026-24308? 5 open source packages ship an affected version, including org.apache.zookeeper:zookeeper and zookeeper. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.zookeeper:zookeeper` | Maven | From 3.8.0 | 3.8.6 | | `org.apache.zookeeper:zookeeper` | Maven | From 3.8.0 | 3.8.6 | | `org.apache.zookeeper:zookeeper` | Maven | From 3.9.0 | 3.9.5 | | `org.apache.zookeeper:zookeeper` | Maven | From 3.9.0 | 3.9.5 | | `zookeeper` | Bitnami | From 3.8.0 | 3.8.6, 3.9.5 | Products: Apache Zookeeper. ## How do I fix CVE-2026-24308? Upgrade org.apache.zookeeper:zookeeper to a fixed version for your release line: 3.8.6 or 3.9.5. ## Is CVE-2026-24308 being exploited? There is no known exploitation of CVE-2026-24308 in the wild and no public exploit code. ## Other vulnerabilities in Apache ZooKeeper - [CVE-2024-51504](https://insights.sbomify.com/CVE-2024-51504/): Apache ZooKeeper: Authentication bypass with IP-based authentication in Admin Server (critical 9.1) - [CVE-2023-44981](https://insights.sbomify.com/CVE-2023-44981/): Apache ZooKeeper: Authorization bypass in SASL Quorum Peer Authentication (critical 9.1) - [CVE-2016-5017](https://insights.sbomify.com/CVE-2016-5017/): Memory corruption in n/a (high 8.1) - [CVE-2026-59739](https://insights.sbomify.com/CVE-2026-59739/): Apache ZooKeeper: Information disclosure via SetWatches reconnect replay (high 7.5) - [CVE-2026-59969](https://insights.sbomify.com/CVE-2026-59969/): Apache ZooKeeper: Improper validation of certificate with host mismatch in FIPS mode (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-24308 and fix it if it is affected. What it is: CVE-2026-24308 is a medium-severity vulnerability in Apache ZooKeeper, published on 7 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-24308 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.zookeeper:zookeeper (Maven): affected from 3.8.0; fixed in 3.8.6 - org.apache.zookeeper:zookeeper (Maven): affected from 3.8.0; fixed in 3.8.6 - org.apache.zookeeper:zookeeper (Maven): affected from 3.9.0; fixed in 3.9.5 - org.apache.zookeeper:zookeeper (Maven): affected from 3.9.0; fixed in 3.9.5 - zookeeper (Bitnami): affected from 3.8.0; fixed in 3.8.6, 3.9.5 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-24308/ (Markdown: https://insights.sbomify.com/CVE-2026-24308/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24308 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24308 - OSV: https://osv.dev/vulnerability/CVE-2026-24308 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-24308/ Summaries are generated and may contain mistakes; the official description above is the record.