Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

CVE-2021-4080 — crater

HIGHFix: crater-invoice/crater@cdc913d

CVE-2021-4080 is a high-severity (CVSS 8.8) Unrestricted File Upload vulnerability in bytefury/crater. 1 public exploit reference exists, so weaponization risk is real. A fix is available for bytefury/crater — see the affected versions and patch details below.

crater is vulnerable to Unrestricted Upload of File with Dangerous Type

Also known asGHSA-wppj-3pjr-9w79
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk
0.00%0.66%1.32%1.97%0.4%1.5%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2021-4080 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
🐘bytefury/crater

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

Description

crater is vulnerable to Unrestricted Upload of File with Dangerous Type

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistbytefury/craterall versions6.0.0composer require bytefury/crater:^6.0.0

Affected Products

1 product · 1 configurations
Application
cratercraterapp
< 6.0.0
range
Exploits & PoCs
1

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 bytefury/crater, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update bytefury/crater to 6.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-4080 is resolved across your whole dependency graph.

  3. Workarounds

    Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Frequently Asked Questions

crater is vulnerable to Unrestricted Upload of File with Dangerous Type
O3 Security · Impact-Aware SCA

Is CVE-2021-4080 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2021-4080: crater — Fixed in 6.0.0