How severe is CVE-2025-8862?

CVE-2025-8862 has a CVSS 4.0 base score of 7.0, rated high severity.

Is CVE-2025-8862 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-8862?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-8862 have an EU (EUVD) identifier?

Yes. CVE-2025-8862 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-24146.

When was CVE-2025-8862 published?

CVE-2025-8862 was published on 2025-08-11 and last updated on 2026-06-17.

CVE-2025-8862

CVE-2025-8862 is a high-severity vulnerability with a CVSS 4.0 base score of 7.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-201.

Key facts

Severity: High (CVSS 4.0 base score 7.0)
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-24146
Weakness: CWE-201
Published: 2025-08-11
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-8862?: 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.
How severe is CVE-2025-8862?: CVE-2025-8862 has a CVSS 4.0 base score of 7.0, rated high severity.
Is CVE-2025-8862 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-8862?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-8862 have an EU (EUVD) identifier?: Yes. CVE-2025-8862 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-24146.
When was CVE-2025-8862 published?: CVE-2025-8862 was published on 2025-08-11 and last updated on 2026-06-17.

References

https://docs.yugabyte.com/preview/secure/vulnerability-disclosure-policy/

Other CWE-201 vulnerabilities

CVE-2025-49408 — Critical (CVSS 10.0): Insertion of Sensitive Information Into Sent Data vulnerability in WPDeveloper Templately allows Retrieve Embedded…
CVE-2024-7205 — Critical (CVSS 9.4): When the device is shared, the homepage module are before 2.19.0 in eWeLink Cloud Service allows Secondary user to…
CVE-2026-39912 — Critical (CVSS 9.1): V2Board 1.6.1 through 1.7.4 and Xboard through 0.1.9 expose authentication tokens in HTTP response bodies of the…
CVE-2025-48749 — Critical (CVSS 9.1): Netwrix Directory Manager (formerly Imanami GroupID) v11.0.0.0 and before & after v.11.1.25134.03 inserts Sensitive…
CVE-2025-11500 — High (CVSS 8.7): Tinycontrol devices such as tcPDU and LAN Controllers LK3.5, LK3.9 and LK4 have two separate authentication…
CVE-2025-48045 — High (CVSS 8.7): An unauthenticated HTTP GET request to the /client.php endpoint will disclose the default administrator user…

Browse all CWE-201 vulnerabilities →