How severe is GHSA-g93m-8x6h-g5gv?

No CVSS score has been assigned to GHSA-g93m-8x6h-g5gv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g93m-8x6h-g5gv?

GHSA-g93m-8x6h-g5gv affects the following packages: org.apache.zookeeper:zookeeper (Maven). Ecosystems affected: Maven.

How do I fix GHSA-g93m-8x6h-g5gv?

Update org.apache.zookeeper:zookeeper to 3.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g93m-8x6h-g5gv is resolved across your whole dependency graph.

How do I detect GHSA-g93m-8x6h-g5gv in my Maven dependencies?

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.

How do I mitigate GHSA-g93m-8x6h-g5gv if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-g93m-8x6h-g5gv actively exploited in the wild?

No public exploit code has been indexed for GHSA-g93m-8x6h-g5gv 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-g93m-8x6h-g5gv?

GHSA-g93m-8x6h-g5gv has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 61th 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-g93m-8x6h-g5gv?

GHSA-g93m-8x6h-g5gv is classified as CWE-290 (CWE-290). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g93m-8x6h-g5gv published, and has it been updated?

GHSA-g93m-8x6h-g5gv was published on November 7, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Apache ZooKeeper: Authentication bypass with IP-based…

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
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-g93m-8x6h-g5gv.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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

When using IPAuthenticationProvider in ZooKeeper Admin Server there is a possibility of Authentication Bypass by Spoofing -- this only impacts IP based authentication implemented in ZooKeeper Admin Server. Default configuration of client's IP address detection in IPAuthenticationProvider, which uses HTTP request headers, is weak and allows an attacker to bypass authentication via spoofing client's IP address in request headers. Default configuration honors X-Forwarded-For HTTP header to read client's IP address. X-Forwarded-For request header is mainly used by proxy servers to identify the client and can be easily spoofed by an attacker pretending that the request comes from a different IP address. Admin Server commands, such as snapshot and restore arbitrarily can be executed on successful exploitation which could potentially lead to information leakage or service availability issues. Users are recommended to upgrade to version 3.9.3, which fixes this issue.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

zookeeperapache

≥ 3.9.0 && < 3.9.3

range

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, 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.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g93m-8x6h-g5gv is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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.

Red HatImportant

This vulnerability is considered an Important severity because it allows an attacker to bypass authentication by spoofing the client’s IP address, exploiting a weakness in ZooKeeper Admin Server's reliance on the `X-Forwarded-For` HTTP header for IP-based authentication. Unlike moderate vulnerabilities that might…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-g93m-8x6h-g5gv (CC BY 4.0)

Frequently Asked Questions

When using IPAuthenticationProvider in ZooKeeper Admin Server there is a possibility of Authentication Bypass by Spoofing -- this only impacts IP based authentication implemented in ZooKeeper Admin Server. Default configuration of client's IP address detection in IPAuthenticationProvider, which uses HTTP request headers, is weak and allows an attacker to bypass authentication via spoofing client's IP address in request headers. Default configuration honors X-Forwarded-For HTTP header to read client's IP address. X-Forwarded-For request header is mainly used by proxy servers to identify the cli

O3 Security · Impact-Aware SCA

Is GHSA-g93m-8x6h-g5gv in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Apache ZooKeeper: Authentication bypass with IP-based authentication in Admin ServerGHSA-g93m-8x6h-g5gv