How severe is CVE-2025-20060?

CVE-2025-20060 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2025-20060 being actively exploited?

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

How do I fix CVE-2025-20060?

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-20060 have an EU (EUVD) identifier?

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

When was CVE-2025-20060 published?

CVE-2025-20060 was published on 2025-02-28 and last updated on 2026-06-17.

CVE-2025-20060

CVE-2025-20060 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. 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-359.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v4: 8.7
EPSS exploit prediction: 0% (29th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-5947
Weakness: CWE-359
Published: 2025-02-28
Last modified: 2026-06-17

Description

An attacker could expose cross-user personal identifiable information (PII) and personal health information transmitted to the Android device via the Dario Health application database.

Frequently asked questions

What is CVE-2025-20060?: An attacker could expose cross-user personal identifiable information (PII) and personal health information transmitted to the Android device via the Dario Health application database.
How severe is CVE-2025-20060?: CVE-2025-20060 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-20060 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-20060?: 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-20060 have an EU (EUVD) identifier?: Yes. CVE-2025-20060 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-5947.
When was CVE-2025-20060 published?: CVE-2025-20060 was published on 2025-02-28 and last updated on 2026-06-17.

References

Other CWE-359 vulnerabilities

CVE-2022-0482 — Critical (CVSS 9.1): Exposure of Private Personal Information to an Unauthorized Actor in GitHub repository alextselegidis/easyappointments…
CVE-2022-2921 — High (CVSS 8.8): Exposure of Private Personal Information to an Unauthorized Actor in GitHub repository notrinos/notrinoserp prior to…
CVE-2025-53625 — High (CVSS 8.7): The DynamicPageList3 extension is a reporting tool for MediaWiki, listing category members and intersections with…
CVE-2025-13008 — High (CVSS 8.6): An information disclosure vulnerability in M-Files Server before versions 25.12.15491.7, 25.8 LTS SR3, 25.2 LTS SR3 and…
CVE-2023-36052 — High (CVSS 8.6): Azure CLI REST Command Information Disclosure Vulnerability
CVE-2024-26192 — High (CVSS 8.2): Microsoft Edge (Chromium-based) Information Disclosure Vulnerability

Browse all CWE-359 vulnerabilities →