What is the CVSS score of CVE-2026-24308?

CVE-2026-24308 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2026-24308?

Within 24 hours: Inventory all systems running ZooKeeper 3.8.5 or 3.9.4 and assess whether client credentials are present in current logfiles; immediately restrict logfile access permissions to authorized administrators only. Within 7 days: Search centralized logging systems, backup archives, and log aggregation platforms for any historical exposure of sensitive configuration data and initiate credential rotation for any potentially compromised secrets. Within 30 days: Upgrade to patched ZooKeeper versions (3.8.6+ or 3.9.5+) and implement log redaction rules to prevent future credential exposure in application logs.

Zookeeper CVE-2026-24308

HIGH

Insertion of Sensitive Information into Log File (CWE-532)

2026-03-07 security@apache.org

GHSA-crhr-qqj8-rpxc

Apache Information Disclosure Zookeeper

7.5

CVSS 3.1 · NVD

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Enable INFO level logging in ZooKeeper client
Exploit

Access client logfiles
Execution

Extract sensitive configuration values
Impact

Compromise credentials or connection details

Vulnerability Assessment

Weakness	CWE CWE-532 OWASP Top 10:2025 A09:2025 - Security Logging & Alerting Failures ASVS 5.0 V16 - Security Logging and Error Handling Log data sanitization
Exploitation Conditions	ZooKeeper 3.8.5 or 3.9.4 with INFO level logging enabled (default or operator-configured). Attacker requires read access to client logfiles where sensitive configuration values are written.
Impact	CVSS 7.5 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: None. User interaction: None.
Exploit ScenarioDerived	An attacker could exploit this vulnerability to expose sensitive information stored in client configuration in the client's logf.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Apache ZooKeeper 3.8.5 and 3.9.4 improperly log sensitive client configuration data at INFO level, allowing unauthenticated remote attackers to extract credentials and other confidential information from application logfiles. The vulnerability affects all platforms and requires no user interaction or special privileges to exploit. No patch is currently available, leaving vulnerable deployments exposed until upgrades to versions 3.8.6 or 3.9.5 are deployed.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:55 CVSS 7.5

RemediationAI

Update to version 3.8.6 or later. Restrict network access to the affected service where possible.

Affected Packages

maven org.apache.zookeeper:zookeeper fix: 3.8.6, 3.9.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in maven

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Classified as CWE-532 (Insertion of Sensitive Information into Log File). Affects Zookeeper. 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.

Know when Zookeeper gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.5 HIGH

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

Red Hat 3.3 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

CVE Published

Mar 07, 2026 - 09:16 nvd

HIGH 7.5

DescriptionNVD

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.

Executive ViewAI

Why It Matters

Apache ZooKeeper versions 3.8.5 and 3.9.4 contain a configuration handling flaw that exposes sensitive client credentials and configuration data in application logfiles, creating a data breach risk for any organization using affected versions. This vulnerability is particularly concerning because it requires no network exploitation-the sensitive data is written directly to logs that may be accessible to unauthorized personnel or retained in centralized logging systems.

Business Impact: High

Compensating Controls

Implement strict file system access controls (chmod 600) on all ZooKeeper logfiles; disable verbose logging of configuration parameters containing credentials; configure centralized log aggregation with automatic redaction/masking of sensitive patterns (passwords, API keys, tokens); implement network segmentation to limit logfile access; enable audit logging on logfile access; consider disabling ZooKeeper client logging until patched. Note: These are temporary mitigations only—patch deployment is required for permanent remediation.

Threat Intelligence Overview

EPSS Score

0.0%

Top 96% exploitable

Data Quality

5 sources

Confidence: Medium

NVD

CVE.org

EPSS Vendor

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Open

Automatable· derived

Yes

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.