GHSA-crhr-qqj8-rpxc — zookeeper
GHSA-crhr-qqj8-rpxc is a CWE-532 vulnerability in org.apache.zookeeper:zookeeper. A fix is available for org.apache.zookeeper:zookeeper — see the affected versions and patch details below.
Apache ZooKeeper has improper handling of configuration values
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-crhr-qqj8-rpxc.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
org.apache.zookeeper:zookeeper☕org.apache.zookeeper:zookeeperReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.zookeeper:zookeeper | ≥ 3.9.0&&< 3.9.5 | 3.9.5org.apache.zookeeper:zookeeper:3.9.5 |
| ☕Maven | org.apache.zookeeper:zookeeper | ≥ 3.8.0&&< 3.8.6 | 3.8.6org.apache.zookeeper:zookeeper:3.8.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.zookeeper:zookeeper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.zookeeper:zookeeper to 3.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-crhr-qqj8-rpxc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-crhr-qqj8-rpxc can be triaged on real exposure rather than presence alone.
Tailored to GHSA-crhr-qqj8-rpxc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat AMQ Broker 7.12.7 | zookeeper | RHSA-2026:14276 |
| Red Hat AMQ Broker 7.13.5 | zookeeper | RHSA-2026:14272 |
| Red Hat AMQ Broker 7.14.0 | zookeeper | RHSA-2026:8509 |
| Streams for Apache Kafka 2.9.4 | zookeeper | RHSA-2026:34608 |
| Red Hat OpenShift AI 2.25 | rhoai/odh-modelmesh-rhel9:1776756834 | RHSA-2026:10184 |
Frequently Asked Questions
Is GHSA-crhr-qqj8-rpxc in your dependencies?
O3 Security finds GHSA-crhr-qqj8-rpxc across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.