Sensitive configuration disclosure via unredacted diagnostics
Published Aug 11, 2025 · Updated Aug 11, 2025
Information exposure in affected YugabyteDB releases allows remote attackers to read sensitive gflag settings via collected diagnostics. The diagnostics collection pipeline transmits server bundles without redacting sensitive gflag configuration values before collection. Network reachability and a high-complexity path are required; the disclosure exposes security-relevant server configuration to the diagnostics recipient.
Summary
What happened
Information exposure in affected YugabyteDB releases allows remote attackers to read sensitive gflag settings via collected diagnostics. The diagnostics collection pipeline transmits server bundles without redacting sensitive gflag configuration values before collection. Network reachability and a high-complexity path are required; the disclosure exposes security-relevant server configuration to the diagnostics recipient.
The record
- CVE
- CVE-2025-8862
- Published
- Aug 11, 2025
- Updated
- Aug 11, 2025
- Vendor
- YugabyteDB, Inc.
- Product
- YugabyteDB
- Classifications
- CWE-201
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2024.1.0 <2024.1.3
- Affected versionversion=2.20.0.0 <2.20.7.0
- Affected versionversion=2.23.0.0 <2.23.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo