CVE-2025-4397
MEDIUMCVSS 6.8/10EPSS 0.13%
Last modified
CVE-2025-4397 is a medium-severity vulnerability rated 6.8/10 on the CVSS scale. 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.. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Medtronic | MyCareLink Patient Monitor 24950 | < February 25, 2026 |
| Medtronic | MyCareLink Patient Monitor 24952 | < February 25, 2026 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2025-4397?
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.
How severe is CVE-2025-4397?
CVE-2025-4397 has a CVSS score of 6.8/10 (MEDIUM severity). The EPSS model estimates a 0.13% probability of exploitation in the next 30 days.
How do I fix CVE-2025-4397?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-43962In LibRaw before 0.21.4, phase_one_correct in decoders/load_…9.1
- CVE-2025-43963In LibRaw before 0.21.4, phase_one_correct in decoders/load_…9.1
- CVE-2025-43964In LibRaw before 0.21.4, tag 0x412 processing in phase_one_c…9.8
- CVE-2025-43965In MIFF image processing in ImageMagick before 7.1.1-44, ima…7.5
- CVE-2025-43966libheif before 1.19.6 has a NULL pointer dereference in Imag…7.5
- CVE-2025-43967libheif before 1.19.6 has a NULL pointer dereference in Imag…7.5
- CVE-2025-43970An issue was discovered in GoBGP before 3.35.0. pkg/packet/m…5.3
- CVE-2025-43971An issue was discovered in GoBGP before 3.35.0. pkg/packet/b…7.5
- CVE-2025-43972An issue was discovered in GoBGP before 3.35.0. An attacker …7.5
- CVE-2025-43973An issue was discovered in GoBGP before 3.35.0. pkg/packet/r…9.8
- CVE-2025-43976The com.enflick.android.tn2ndLine application through 24.17.…5.5
- CVE-2025-43977The com.skt.prod.dialer application through 12.5.0 for Andro…5.5
Are you affected by CVE-2025-4397?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST