<?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-05T02:58:33.192289+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-214040</id>
    <title>EUVD-2026-214040</title>
    <updated>2026-10-05T02:58:33.284776+00:00</updated>
    <content>EUVD-2026-214040</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-214040"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2020-17354</id>
    <title>fkie_cve-2020-17354</title>
    <updated>2026-10-05T02:58:33.284828+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>LilyPond before 2.24 allows attackers to bypass the -dsafe protection mechanism via output-def-lookup or output-def-scope, as demonstrated by dangerous Scheme code in a .ly file that causes arbitrary code execution during conversion to a different file format. NOTE: in 2.24 and later versions, safe mode is removed, and the product no longer tries to block code execution when external files are used.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2020-17354"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vm3h-24gm-v3q6</id>
    <title>GHSA-vm3h-24gm-v3q6</title>
    <updated>2026-10-05T02:58:33.284892+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>LilyPond before 2.24 allows attackers to bypass the -dsafe protection mechanism via output-def-lookup or output-def-scope, as demonstrated by dangerous Scheme code in a .ly file that causes arbitrary code execution during conversion to a different file format. NOTE: in 2.24 and later versions, safe mode is removed, and the product no longer tries to block code execution when external files are used.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vm3h-24gm-v3q6"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2020-17354</id>
    <title>gsd-2020-17354</title>
    <updated>2026-10-05T02:58:33.284912+00:00</updated>
    <content>gsd-2020-17354</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2020-17354"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2023:0137-1</id>
    <title>openSUSE-SU-2023:0137-1 — Security update for guile1, lilypond</title>
    <updated>2026-10-05T02:58:33.284925+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for guile1, lilypond</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2023:0137-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-17354</id>
    <title>UBUNTU-CVE-2020-17354</title>
    <updated>2026-10-05T02:58:33.284946+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: lilypond, Ubuntu:18.04:LTS: lilypond, Ubuntu:20.04:LTS: lilypond</p>
<p>LilyPond before 2.24 allows attackers to bypass the -dsafe protection mechanism via output-def-lookup or output-def-scope, as demonstrated by dangerous Scheme code in a .ly file that causes arbitrary code execution during conversion to a different file format. NOTE: in 2.24 and later versions, safe mode is removed, and the product no longer tries to block code execution when external files are used.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-17354"/>
  </entry>
</feed>
