Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

CVE-2020-28468 — pwntools

CRITICALFix: Gallopsled/pwntools#1732

CVE-2020-28468 is a critical-severity (CVSS 9.8) CWE-74 vulnerability in pwntools. 2 public exploit references exist, so weaponization risk is real. A fix is available for pwntools — see the affected versions and patch details below.

pwntools Server-Side Template Injection (SSTI) vulnerability

Also known asGHSA-7xc5-ggpp-g249PYSEC-2021-72SNYK-PYTHON-PWNTOOLS-1047345
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.4%probability of exploitation in next 30 days
Lower Risk+0.18%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk
3.66%4.21%4.77%5.32%4.8%4.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-28468 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐍pwntools

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

This affects the package pwntools before 4.3.1. The shellcraft generator for affected versions of this module are vulnerable to Server-Side Template Injection (SSTI), which can lead to remote code execution.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIpwntoolsall versions4.3.1pip install --upgrade 'pwntools==4.3.1'

Affected Products

1 product · 1 configurations
Application
pwntoolspwntools_project
< 4.3.1
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pwntools, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update pwntools to 4.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28468 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

This affects the package pwntools before 4.3.1. The shellcraft generator for affected versions of this module are vulnerable to Server-Side Template Injection (SSTI), which can lead to remote code execution.
O3 Security · Impact-Aware SCA

Is CVE-2020-28468 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2020-28468: pwntools RCE — Fixed in 4.3.1