CVE-2020-17354

HIGHNVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2023-04-16. NVD baseline CVSS 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
55(Track*)
EG Risk 55/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

April 15, 2023

Last Modified

February 6, 2025

References (16)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
lilypond2.22.0-10 ... 2.24.4-6 (20 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
lilypond—2.22.1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
lilypond—2.22.1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
lilypond—2.22.1-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 130 total refreshes for this CVE.

  1. 2026-08-25 13:45 UTCEPSS rescore
  2. 2026-08-21 23:45 UTCEPSS rescore
  3. 2026-08-20 22:52 UTCEPSS rescore
  4. 2026-08-19 17:00 UTCEPSS rescore
  5. 2026-08-18 13:44 UTCEPSS rescore
  6. 2026-08-17 20:29 UTCOSV refresh
  7. 2026-08-17 13:43 UTCEPSS rescore
  8. 2026-08-16 14:52 UTCEPSS rescore
  9. 2026-08-16 02:11 UTCEPSS rescore
  10. 2026-08-15 01:26 UTCEPSS rescore
  11. 2026-08-13 21:57 UTCEPSS rescore
  12. 2026-08-12 13:47 UTCEPSS rescore
  13. 2026-08-09 13:43 UTCEPSS rescore
  14. 2026-08-08 16:33 UTCEPSS rescore
  15. 2026-08-07 16:23 UTCEPSS rescore
  16. 2026-08-06 13:43 UTCEPSS rescore
  17. 2026-08-05 19:14 UTCEPSS rescore
  18. 2026-08-04 15:06 UTCEPSS rescore
  19. 2026-08-04 10:34 UTCEPSS rescore
  20. 2026-08-03 10:32 UTCEPSS rescore
  21. 2026-08-02 15:57 UTCOSV refresh
  22. 2026-08-02 02:23 UTCEPSS rescore
  23. 2026-08-01 04:12 UTCEPSS rescore
  24. 2026-07-30 16:25 UTCEPSS rescore
  25. 2026-07-30 01:27 UTCEPSS rescore
Show 75 more
  1. 2026-07-28 15:32 UTCEPSS rescore
  2. 2026-07-27 14:06 UTCEPSS rescore
  3. 2026-07-26 14:51 UTCEPSS rescore
  4. 2026-07-25 14:15 UTCEPSS rescore
  5. 2026-07-25 14:14 UTCEPSS rescore
  6. 2026-07-24 14:14 UTCEPSS rescore
  7. 2026-07-23 14:15 UTCEPSS rescore
  8. 2026-07-23 14:15 UTCEPSS rescore
  9. 2026-07-23 01:50 UTCEG score recompute
  10. 2026-07-22 22:35 UTCEG score recompute
  11. 2026-07-22 14:05 UTCEPSS rescore
  12. 2026-07-21 15:22 UTCEPSS rescore
  13. 2026-07-21 15:22 UTCEPSS rescore
  14. 2026-07-20 17:04 UTCEPSS rescore
  15. 2026-07-20 17:04 UTCEPSS rescore
  16. 2026-07-19 02:26 UTCEPSS rescore
  17. 2026-07-19 02:26 UTCEPSS rescore
  18. 2026-07-18 10:02 UTCEPSS rescore
  19. 2026-07-16 16:59 UTCEPSS rescore
  20. 2026-07-15 23:23 UTCOSV refresh
  21. 2026-07-15 16:55 UTCEPSS rescore
  22. 2026-07-15 01:57 UTCEPSS rescore
  23. 2026-07-13 22:27 UTCEPSS rescore
  24. 2026-07-13 22:27 UTCEPSS rescore
  25. 2026-07-13 06:10 UTCEPSS rescore
  26. 2026-07-13 06:10 UTCEPSS rescore
  27. 2026-07-12 05:44 UTCEPSS rescore
  28. 2026-07-11 08:25 UTCEPSS rescore
  29. 2026-07-11 08:25 UTCEPSS rescore
  30. 2026-07-09 19:07 UTCEPSS rescore
  31. 2026-07-07 13:43 UTCEPSS rescore
  32. 2026-07-07 13:43 UTCEPSS rescore
  33. 2026-07-06 16:25 UTCEPSS rescore
  34. 2026-07-06 16:25 UTCEPSS rescore
  35. 2026-07-06 02:21 UTCEPSS rescore
  36. 2026-07-06 02:21 UTCEPSS rescore
  37. 2026-07-05 02:27 UTCEPSS rescore
  38. 2026-07-04 06:29 UTCEPSS rescore
  39. 2026-07-04 06:28 UTCEPSS rescore
  40. 2026-07-01 15:03 UTCEPSS rescore
  41. 2026-06-30 23:20 UTCEPSS rescore
  42. 2026-06-30 23:20 UTCEPSS rescore
  43. 2026-06-29 14:04 UTCEPSS rescore
  44. 2026-06-28 14:05 UTCEPSS rescore
  45. 2026-06-28 04:54 UTCEPSS rescore
  46. 2026-06-28 04:54 UTCEPSS rescore
  47. 2026-06-28 00:04 UTCOSV refresh
  48. 2026-06-27 03:06 UTCEPSS rescore
  49. 2026-06-25 13:47 UTCEPSS rescore
  50. 2026-06-24 14:03 UTCEPSS rescore
  51. 2026-06-24 14:03 UTCEPSS rescore
  52. 2026-06-23 21:31 UTCEPSS rescore
  53. 2026-06-23 21:31 UTCEPSS rescore
  54. 2026-06-22 14:23 UTCEPSS rescore
  55. 2026-06-22 14:23 UTCEPSS rescore
  56. 2026-06-21 14:54 UTCEPSS rescore
  57. 2026-06-21 14:54 UTCEPSS rescore
  58. 2026-06-21 01:57 UTCEPSS rescore
  59. 2026-06-21 01:57 UTCEPSS rescore
  60. 2026-06-19 19:23 UTCEPSS rescore
  61. 2026-06-18 17:50 UTCEPSS rescore
  62. 2026-06-17 17:50 UTCEPSS rescore
  63. 2026-06-16 17:50 UTCEPSS rescore
  64. 2026-06-16 17:50 UTCEPSS rescore
  65. 2026-06-15 17:46 UTCEPSS rescore
  66. 2026-06-14 23:15 UTCEPSS rescore
  67. 2026-06-13 22:58 UTCEPSS rescore
  68. 2026-06-13 22:58 UTCEPSS rescore
  69. 2026-06-12 23:10 UTCEPSS rescore
  70. 2026-06-11 13:58 UTCEPSS rescore
  71. 2026-06-10 22:16 UTCEPSS rescore
  72. 2026-06-10 22:16 UTCEPSS rescore
  73. 2026-06-10 13:20 UTCEPSS rescore
  74. 2026-06-10 10:47 UTCOSV refresh
  75. 2026-06-08 14:15 UTCEPSS rescore

Frequently asked(5)

What is CVE-2020-17354?
CVE-2020-17354 is a high vulnerability published on April 15, 2023. 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…
When was CVE-2020-17354 disclosed?
CVE-2020-17354 was first published in the National Vulnerability Database on April 15, 2023, with the most recent update on February 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-17354 actively exploited?
CVE-2020-17354 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.8% of all scored CVEs.
What is the CVSS score of CVE-2020-17354?
CVE-2020-17354 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2020-17354?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-17354, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-17354

Explore →

Is Your Infrastructure Affected by CVE-2020-17354?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs