Skip to main content
CVE-2025-8862VulnerabilityPublished

CVE-2025-8862: YugabyteDB · Insertion of Sensitive Information Into Sent Data

Affects YugabyteDBSource CVE Database V5

0

Not known to be exploited · CVSS 7.0 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
YugabyteDB Inc YugabyteDBAffected
  • =2024.1.0
  • =2.20.0.0
  • =2.23.0.0
Fixed in–

AI-suggested

1. Immediate upgrade: European organizations should prioritize upgrading YugabyteDB to the latest patched version where sensitive gflag information is properly redacted in diagnostics. 2. Configuration review: Audit current YugabyteDB configurations to identify any sensitive flags that could be exposed and minimize the use of sensitive flags where possible. 3. Network segmentation: Restrict network access to YugabyteDB diagnostic endpoints to trusted internal networks only, reducing exposure to external attackers. 4. Monitoring and logging: Implement enhanced monitoring to detect unusual access patterns or data exfiltration attempts related to diagnostic data. 5. Disable telemetry if feasible: Temporarily disable diagnostic telemetry collection if upgrading is not immediately possible, balancing operational needs with security risks. 6. Incident response readiness: Prepare incident response plans to address potential information leakage and subsequent exploitation attempts. 7. Vendor communication: Maintain close communication with YugabyteDB Inc for updates, patches, and best practices related to this vulnerability.

Description

YugabyteDB has been collecting diagnostics information from YugabyteDB servers, which may include sensitive gflag configurations. To mitigate this, we recommend upgrading the database to a version where this information is properly redacted.

References

Community reviews

Loading reviews…