CVE-2020-17354: LilyPond before 2.24 allows attackers to bypass the -dsafe protection mechanism via output-def-lookup or outpu

Q: How do I fix CVE-2020-17354?

lilypond: upgrade to 2.24.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-17354 being exploited?

CVE-2020-17354 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-17354 affect?

CVE-2020-17354 affects lilypond. Severity is high (CVSS 8.6). 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 di

Q: How urgent is CVE-2020-17354?

Priority 44/100. High severity; Public exploit reference

This month

HIGH 8.6UPGRADE

CVE-2020-17354 is a high-severity flaw (CVSS 8.6) affecting lilypond. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.6 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-863
Published	2023-04-15
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: lilypond

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-04-15 22:15 UTCPublished CVE record published
2026-06-17 02:58 UTCUpdated Record last modified

lilypond lilypond UPGRADE

Affected: < 2.24.0

Fixed in: 2.24.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy lilypond || rpm -q lilypond || lilypond --version

2. UPGRADE to 2.24.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade lilypond

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade lilypond

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-17354?

lilypond: upgrade to 2.24.0. Exact commands for each OS are on this page.

Is CVE-2020-17354 being exploited?

CVE-2020-17354 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-17354 affect?

CVE-2020-17354 affects lilypond. Severity is high (CVSS 8.6). 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 di

How urgent is CVE-2020-17354?

Priority 44/100. High severity; Public exploit reference

References

← Back to latest CVEs