# CVE-2025-4397: Medtronic MyCareLink Patient Monitor Data Encryption Weakness

> Attackers can recover stored credentials to modify encrypted data on Medtronic MyCareLink Patient Monitors due to weak credential storage.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-f8v9-5h44-4grj

## What is CVE-2025-4397?

CVE-2025-4397 is a medium-severity vulnerability in Medtronic MyCareLink Patient Monitor 24950, published on 7 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Medtronic MyCareLink Patient Monitor uses per-product credentials that are stored in a recoverable format. An attacker can use these credentials to modify encrypted drive data.

Weakness: CWE-313 (Cleartext Storage in a File or on Disk)

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


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

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

## Is CVE-2025-4397 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4397 is a medium-severity vulnerability in Medtronic MyCareLink Patient Monitor 24950, published on 7 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4397 in the wild and no public exploit code.

Affected product: Medtronic MyCareLink Patient Monitor 24950. 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-4397/ (Markdown: https://insights.sbomify.com/CVE-2025-4397/index.md)
```

## Sources

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

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