# CVE-2025-20060: Information disclosure in Dario Application Database and Internet-based Server Infrastructure

> An attacker can expose cross-user personal health information stored in the Dario Health Android application database.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2025
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-26gv-chv5-g7q6

## What is CVE-2025-20060?

CVE-2025-20060 is a high-severity vulnerability in Dario Application Database and Internet-based Server Infrastructure, published on 28 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-20060?


## How do I fix CVE-2025-20060?

No fix has been published for CVE-2025-20060 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-20060 being exploited?

There is no known exploitation of CVE-2025-20060 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20060 and fix it if it is affected.

What it is: CVE-2025-20060 is a high-severity vulnerability in Dario Application Database and Internet-based Server Infrastructure, published on 28 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20060 in the wild and no public exploit code.

Affected product: Dario Application Database and Internet-based Server Infrastructure. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-20060/ (Markdown: https://insights.sbomify.com/CVE-2025-20060/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20060
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20060
- OSV: https://osv.dev/vulnerability/CVE-2025-20060

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-20060/
Summaries are generated and may contain mistakes; the official description above is the record.