CVE-2020-15271

CRITICALNVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under NVD CVSS v3. EPSS exploit probability: 2.0%, top 21% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.3Exploit: None knownExposed: 0

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

In lookatme (python/pypi package) versions prior to 2.3.0, the package automatically loaded the built-in "terminal" and "file_loader" extensions. Users that use lookatme to render untrusted markdown may have malicious shell commands automatically run on their system. This is fixed in version 2.3.0. As a workaround, the lookatme/contrib/terminal.py and lookatme/contrib/file_loader.py files may be manually deleted. Additionally, it is always recommended to be aware of what is being rendered with lookatme.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
47(Track)
EG Risk 47/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
Severity93% × 45%
Exploitation2% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
83%
KEV
Not listed

Published

October 26, 2020

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
generic

lookatme · PyPI

https://pypi.org/project/lookatme/#history
github Patch Available

Markdown-supplied Shell Command Execution · Advisory · d0c-s4vage/lookatme · GitHub

https://github.com/d0c-s4vage/lookatme/security/advisories/GHSA-c84h-w6cr-5v8q
github_release Patch Available

v2.3.0

Patch available: d0c-s4vage/lookatme v2.3.0

https://github.com/d0c-s4vage/lookatme/releases/tag/v2.3.0
github_pr Patch Available

Adds warnings about loading extensions

Patch available: d0c-s4vage/lookatme v2.3.0 (PR #110 merged 2020-10-23)

https://github.com/d0c-s4vage/lookatme/pull/110
github_commit Patch Available

commit 72fe36b784b2 (d0c-s4vage/lookatme)

Patch available: d0c-s4vage/lookatme v2.3.0 (contains commit 72fe36b784b2)

https://github.com/d0c-s4vage/lookatme/commit/72fe36b784b234548d49dae60b840c37f0eb8d84

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
lookatme—2.3.0-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
lookatme—2.3.0-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
lookatme—2.3.0-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
lookatme—2.3.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
lookatme0.0.2 ... 2.2.0 (17 versions)2.3.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 161 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-15271?
CVE-2020-15271 is a critical vulnerability published on October 26, 2020. In lookatme (python/pypi package) versions prior to 2.3.0, the package automatically loaded the built-in "terminal" and "fileloader" extensions. Users that use lookatme to render untrusted markdown may have malicious shell commands automatically run on their system. This is fixed in version 2.3.0.…
When was CVE-2020-15271 disclosed?
CVE-2020-15271 was first published in the National Vulnerability Database on October 26, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-15271 actively exploited?
CVE-2020-15271 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 17.4% of all scored CVEs.
What is the CVSS score of CVE-2020-15271?
CVE-2020-15271 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2020-15271?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-15271, 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-15271

Explore →

Is Your Infrastructure Affected by CVE-2020-15271?

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

Book a Demo →Browse All CVEs