<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T10:01:23.322148+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-277847</id>
    <title>EUVD-2026-277847</title>
    <updated>2026-10-02T10:01:23.378629+00:00</updated>
    <content>EUVD-2026-277847</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-277847"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-4393</id>
    <title>fkie_cve-2025-4393</title>
    <updated>2026-10-02T10:01:23.378678+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>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.</p>
<p>This issue affects MyCareLink Patient Monitor models 24950 and 24952: before June 25, 2025</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-4393"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-783m-53vh-rmp2</id>
    <title>GHSA-783m-53vh-rmp2</title>
    <updated>2026-10-02T10:01:23.378724+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>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.</p>
<p>This issue affects MyCareLink Patient Monitor models 24950 and 24952: before June 25, 2025</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-783m-53vh-rmp2"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/icsma-25-205-01</id>
    <title>ICSMA-25-205-01 — Medtronic MyCareLink Patient Monitor (Update A)</title>
    <updated>2026-10-02T10:01:23.378743+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Medtronic MyCareLink Patient Monitor uses an unencrypted filesystem on internal storage, which allows an attacker with physical access to read and modify files. Medtronic MyCareLink Patient Monitor has a built-in user account with an empty password, which allows an attacker with physical access to log in with no password and access/modify system functionality. 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. Medtronic MyCareLink Patient Monitor uses per-product credentials that are stored in a recoverable format. An attacker can use these credentials for network authentication. Medtronic MyCareLink Patient Monitor has an internal serial interface, which allows an attacker with physical access to access a login prompt via a UART terminal. 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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/icsma-25-205-01"/>
  </entry>
</feed>
