CVE-2025-8863: YugabyteDB · Cleartext Transmission
Affects YugabyteDBSource CVE Database V5
Not known to be exploited · CVSS 7.0 High.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% 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:LExploitation evidence
Disclosed: evidence found.
CVE published 11 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| YugabyteDB Inc YugabyteDB | Affected
| Fixed in– |
AI-suggested
European organizations should immediately audit their YugabyteDB deployments to identify affected versions (2024.1.0, 2.20.0.0, 2.23.0.0). Until official patches are released, organizations should enforce encryption for all diagnostic and telemetry data transmissions by configuring YugabyteDB to use HTTPS or secure tunnels such as VPNs or SSH tunnels for diagnostic endpoints. Network segmentation should be applied to restrict access to diagnostic interfaces to trusted internal hosts only. Monitoring network traffic for unencrypted diagnostic data can help detect potential exploitation attempts. Additionally, organizations should review and harden network perimeter defenses and employ intrusion detection systems capable of identifying suspicious traffic patterns. When patches become available, prompt application is critical. Finally, organizations should update their incident response plans to include this vulnerability and educate relevant personnel about the risks of unencrypted diagnostic data.
Description
YugabyteDB diagnostic information was transmitted over HTTP, which could expose sensitive data during transmission