CVE-2020-15271: In lookatme (python/pypi package) versions prior to 2.3.0, the package automatically loaded the built-in "term

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

lookatme: upgrade to 2.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-15271 being exploited?

CVE-2020-15271 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-15271 affect?

CVE-2020-15271 affects lookatme. Severity is critical (CVSS 9.3). 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 automat

Q: How urgent is CVE-2020-15271?

Priority 58/100. Critical severity; Public exploit reference

This month

CRITICAL 9.3UPGRADE

CVE-2020-15271 is a critical-severity flaw (CVSS 9.3) affecting lookatme. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 re

Why this priority

Critical severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	9.3 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	2.3% (top 17%)
CISA exploited list	No
Weakness	CWE-78
Published	2020-10-26
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: lookatme project

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

Am I affected?

Timeline

2020-10-26 18:15 UTCPublished CVE record published
2026-06-17 02:56 UTCUpdated Record last modified

lookatme project lookatme UPGRADE

Affected: < 2.3.0

Fixed in: 2.3.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 2.3.0 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade lookatme

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-15271?

lookatme: upgrade to 2.3.0. Exact commands for each OS are on this page.

Is CVE-2020-15271 being exploited?

CVE-2020-15271 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-15271 affect?

CVE-2020-15271 affects lookatme. Severity is critical (CVSS 9.3). 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 automat

How urgent is CVE-2020-15271?

Priority 58/100. Critical severity; Public exploit reference

Software pages

Python vulnerabilities · PyPI packages vulnerabilities

References

← Back to latest CVEs