How severe is GHSA-2hmj-97jw-28jh?

GHSA-2hmj-97jw-28jh has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2hmj-97jw-28jh?

GHSA-2hmj-97jw-28jh affects the following packages: org.apache.zookeeper:zookeeper (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2hmj-97jw-28jh?

Update org.apache.zookeeper:zookeeper to 3.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2hmj-97jw-28jh is resolved across your whole dependency graph.

How do I detect GHSA-2hmj-97jw-28jh in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.zookeeper:zookeeper. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2hmj-97jw-28jh if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-2hmj-97jw-28jh?

O3 pinpoints whether GHSA-2hmj-97jw-28jh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2hmj-97jw-28jh actively exploited in the wild?

No public exploit code has been indexed for GHSA-2hmj-97jw-28jh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2hmj-97jw-28jh?

GHSA-2hmj-97jw-28jh has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2hmj-97jw-28jh?

GHSA-2hmj-97jw-28jh is classified as CWE-280 (CWE-280). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2hmj-97jw-28jh published, and has it been updated?

GHSA-2hmj-97jw-28jh was published on September 24, 2025 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-2hmj-97jw-28jh

MEDIUM

Apache ZooKeeper: Insufficient Permission Check in AdminServer Snapshot/Restore Commands

Also known asBIT-zookeeper-2025-58457CVE-2025-58457

Published

Sep 24, 2025

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk21th percentile+0.18%

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.

Blast Radius

1 pkg affected

☕org.apache.zookeeper:zookeeper

Real-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 permission checks in the AdminServer allow an authenticated client with insufficient privileges to invoke the snapshot and restore commands. The intended requirement is authentication and authorization on the root path (/) with ALL permission for these operations; however, affected versions permit invocation without that level of authorization. The primary risk is disclosure of cluster state via snapshots to a lesser-privileged client.

Affected: org.apache.zookeeper:zookeeper 3.9.0 through 3.9.3.
Fixed: 3.9.4 (ZOOKEEPER-4964 “check permissions individually during admin server auth”).
Mitigations:
- Disable both commands (admin.snapshot.enabled, admin.restore.enabled).
- Disable AdminServer (admin.enableServer).
- Ensure the root ACL is not open; note that ZooKeeper ACLs are not recursive.
- Upgrade to 3.9.4.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.zookeeper:zookeeper`	≥ 3.9.0&&< 3.9.4	3.9.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.zookeeper:zookeeper. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.zookeeper:zookeeper to 3.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2hmj-97jw-28jh 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 pinpoints whether GHSA-2hmj-97jw-28jh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2hmj-97jw-28jh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Improper permission checks in the AdminServer allow an authenticated client with insufficient privileges to invoke the `snapshot` and `restore` commands. The intended requirement is authentication and authorization on the root path (`/`) with **ALL** permission for these operations; however, affected versions permit invocation without that level of authorization. The primary risk is disclosure of cluster state via snapshots to a lesser-privileged client. * **Affected:** `org.apache.zookeeper:zookeeper` 3.9.0 through 3.9.3. * **Fixed:** 3.9.4 (ZOOKEEPER-4964 “check permissions individually

O3 Security · Impact-Aware SCA

Is GHSA-2hmj-97jw-28jh in your dependencies?

O3 detects GHSA-2hmj-97jw-28jh across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works