CVE-2025-8863: High severity Yugabyte YugabyteDB vulnerability
Published Aug 11, 2025
·Updated
YugabyteDB diagnostic information was transmitted over HTTP, which could expose sensitive data during transmission
Affected Software
1 affected component
Yugabyte YugabyteDB
Event History
Aug 11, 2025
CVE Published
via MITRE·01:03 PM
Data Sourced
via MITRE·01:03 PM
DescriptionWeakness
Data Sourced
via NVD·01:15 PM
DescriptionSeverityWeakness
Oct 5, 57909
Event
via FIRST·09:44 PM
Frequently Asked Questions
1
What is the severity of CVE-2025-8863?
CVE-2025-8863 has been classified as a moderate severity vulnerability.
2
How do I fix CVE-2025-8863?
To address CVE-2025-8863, configure YugabyteDB to use HTTPS instead of HTTP for transmitting diagnostic information.
3
What impact does CVE-2025-8863 have on data security?
CVE-2025-8863 can expose sensitive diagnostic data during transmission, increasing the risk of data interception.
4
Is CVE-2025-8863 specific to certain versions of YugabyteDB?
CVE-2025-8863 affects all versions of YugabyteDB that transmit diagnostic information over HTTP.
5
Are there any workarounds for CVE-2025-8863?
Yes, one immediate workaround for CVE-2025-8863 is to ensure that all connections to YugabyteDB use secure protocols.