How serious is CVE-2026-24281?

This vulnerability has a CVSS score of 7.4 out of 10, classified as HIGH severity. Proof-of-concept exploit code is publicly available, making this an active threat.

Is there exploit code available for CVE-2026-24281?

Yes, proof-of-concept exploit code for CVE-2026-24281 is publicly available on GitHub and security research platforms. This increases the risk of active exploitation.

Which products are affected by CVE-2026-24281?

CVE-2026-24281 affects apache zookeeper. Check the full CVE details for specific version information.

How do I fix CVE-2026-24281?

To remediate CVE-2026-24281, check for security patches from apache. Apply all available updates and security patches. If no patch is available, implement recommended workarounds or security controls to mitigate the risk.

CVE-2026-24281

High

|7.4

Exploit Available

Plain English Summary

AI-powered analysis for quick understanding

This vulnerability allows attackers to impersonate ZooKeeper servers or clients by controlling or spoofing reverse DNS records, potentially tricking systems into trusting them. However, the attacker must also present a valid certificate that is recognized by the system, making it more challenging to exploit.

Technical Description

Hostname verification in Apache ZooKeeper ZKTrustManager falls back to reverse DNS (PTR) when IP SAN validation fails, allowing attackers who control or spoof PTR records to impersonate ZooKeeper servers or clients with a valid certificate for the PTR name. It's important to note that attacker must present a certificate which is trusted by ZKTrustManager which makes the attack vector harder to exploit. Users are recommended to upgrade to version 3.8.6 or 3.9.5, which fixes this issue by introducing a new configuration option to disable reverse DNS lookup in client and quorum protocols.

CVSS Vector Analysis

Attack VectorNetwork

Attack ComplexityHigh

Privileges RequiredNone

User InteractionNone

Confidentiality ImpactHigh

Integrity ImpactHigh

Availability ImpactNone

ScopeUnchanged

Vector String

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploit Resources

Search for proof-of-concept code and exploit modules

GitHub Search Exploit-DB Nuclei Templates Metasploit Vulners

Official References

NIST NVD

Est. Bounty

$1,842($1K-$5K)

Vendor Response

Grade APatched in 3 days

Quick Information

Published

Mar 7, 2026

about 1 month ago

Last Modified

Mar 10, 2026

28 days ago

Vendor

apache

Product

zookeeper

Related Vulnerabilities

CVE-2025-66249Medium

This vulnerability allows an attacker to access files outside of the intended directory on an Apache Livy server, potentially exposing sensitive data. It can only be exploited if the server is configured with a non-default setting for local directory access, so users should upgrade to version 0.9.0 to protect against this risk.

CVE-2025-60012Medium

This vulnerability allows an attacker to access files they shouldn't be able to reach by sending specially crafted requests to Apache Livy's REST or JDBC interface. To exploit this, the attacker must already have access to these interfaces and be able to include specific Spark configuration values in their requests.

CVE-2026-25604Medium

An attacker could gain unauthorized access to different AWS instances by reusing SAML authentication responses from other instances, potentially bypassing access controls. This vulnerability occurs because the system does not verify the origin of the SAML response against the actual instance URL, so it's crucial to upgrade to version 9.22.0 of the provider if you're using AWS Auth Manager.

CVE-2025-69219High

This vulnerability allows an attacker with access to the database to run unauthorized code, effectively giving them the same permissions as the original creator of workflows in Airflow. While direct access to the database is uncommon and not recommended, upgrading to version 6.0.0 of the provider is essential to eliminate this risk.

CVE-2026-24713Critical

This vulnerability allows an attacker to send malicious input to Apache IoTDB, potentially leading to unauthorized access or manipulation of data. It affects versions 1.0.0 to 1.3.6 and 2.0.0 to 2.0.6, so users should upgrade to the latest versions to protect against this risk.