CVE-2020-17353 [Critical] | Security Vulnerability in Lilypond

CVE-2020-17353 is rated High Risk (68.9/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 2.37%). EPSS rose +1.11% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	1.26%	2.37%	+1.11%
2	2025-03-30	3.25%	1.26%	-1.98%
3	2025-03-29	—	3.25%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

1.26%

2.37%

+1.11%

2025-03-30

3.25%

1.26%

-1.98%

2025-03-29

—

3.25%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	5.9	[email protected]
7.5	2.0	HIGH	`AV:N/AC:L/Au:N/C:P/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	10.0	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

9.8

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

5.9

[email protected]

7.5

2.0

HIGH

AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

10.0

6.4

[email protected]

OS Trackers for CVE-2020-17353

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2020-17353 not yet assigned priority: Debian including 1 source packages (lilypond), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2020-17353
`ubuntu`	medium	CVE-2020-17353 medium priority: Ubuntu including 1 source packages (lilypond), 16 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 10, needed 4, DNE 1, ignored 1.	https://ubuntu.com/security/CVE-2020-17353

Affected software / configurations for CVE-2020-17353

Vendor	Product	Version	Raw CPE
lilypond	lilypond	<= 2.20.0	cpe:2.3:a:lilypond:lilypond::::::::
lilypond	lilypond	>= 2.21.0, <= 2.21.4	cpe:2.3:a:lilypond:lilypond::::::::
fedoraproject	fedora	31	cpe:2.3:o:fedoraproject:fedora:31:::::::*
fedoraproject	fedora	32	cpe:2.3:o:fedoraproject:fedora:32:::::::*
debian	debian_linux	10.0	cpe:2.3:o:debian:debian_linux:10.0:::::::*
opensuse	backports_sle	15.0	cpe:2.3:a:opensuse:backports_sle:15.0:sp2::::::
opensuse	leap	15.2	cpe:2.3:o:opensuse:leap:15.2:::::::*

References for CVE-2020-17353

URL	Tags
http://git.savannah.gnu.org/gitweb/?p=lilypond.git%3Ba=commit%3Bh=b84ea4740f3279516905c5db05f4074e777c16ff
http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00064.html	Mailing List Third Party Advisory
http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00076.html	Mailing List Third Party Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QG2JUV4UTIA27JUE6IZLCEFP5PYSFPF4/
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/W2JYMVLTPSNYS5F7TBHKIXUZZJIJAMRX/
https://www.debian.org/security/2020/dsa-4756	Third Party Advisory

URL

CVE-2020-17353

Exploit prediction scoring system (EPSS) score for CVE-2020-17353

Common vulnerability scoring system (CVSS) metrics for CVE-2020-17353

Weakness enumeration for CVE-2020-17353

OS Trackers for CVE-2020-17353

Affected software / configurations for CVE-2020-17353

References for CVE-2020-17353