Skip to content
Fencer Vulns
medium 6.5

CVE-2025-4393 json

Medtronic MyCareLink Patient Monitor Deserialization Vulnerability

published 2025-07-24 15 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-22528

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

Medtronic MyCareLink Patient Monitor has an internal service that deserializes data, which allows a local attacker to interact with the service by crafting a binary payload to crash the service or elevate privileges.

This issue affects MyCareLink Patient Monitor models 24950 and 24952: before June 25, 2025

Patch / fix

  • Medtronic MyCareLink Patient Monitor 24950 June 25, 2025
  • Medtronic MyCareLink Patient Monitor 24952 June 25, 2025

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSMA-25-205-01 updated cvss 6.5

Medtronic MyCareLink Patient Monitor (Update A)

  • Medtronic MyCareLink Patient Monitor model 24950 Medtronic MyCareLink Patient Monitor model 24952
    affected: mitigation “Medtronic recommends the following actions:” medtronic.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
15 mo ago

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:H

Affected products

  • Medtronic MyCareLink Patient Monitor 24950
  • Medtronic MyCareLink Patient Monitor 24952

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.