How severe is CVE-2021-3129?

CVE-2021-3129 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-3129?

CVE-2021-3129 affects the following packages: facade/ignition (Packagist), facade/ignition (Packagist), facade/ignition (Packagist), facade/ignition (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2021-3129?

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

How do I detect CVE-2021-3129 in my Packagist dependencies?

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

How do I mitigate CVE-2021-3129 if there is no patch (or I can't update yet)?

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.

Is CVE-2021-3129 actively exploited in the wild?

Yes. There are 40 known exploit references for CVE-2021-3129, including 1 documented proof-of-concept exploit on Exploit-DB and 24 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-3129?

CVE-2021-3129 has an EPSS (Exploit Prediction Scoring System) score of 99.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2021-3129 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2021-3129 (Laravel Ignition File Upload Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-09-18. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-10-09. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Is there exploit tooling available for CVE-2021-3129?

A Nuclei detection template exists for CVE-2021-3129, meaning automated scanners can fingerprint it. A Metasploit module references CVE-2021-3129, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2021-3129 published, and has it been updated?

CVE-2021-3129 was published on January 12, 2021 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2021-3129 — ignition

CRITICALFix: facade/ignition#334

CVE-2021-3129 is a critical-severity (CVSS 9.8) remote code execution vulnerability in facade/ignition. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-09-18) and has been used in ransomware campaigns — treat it as actively exploited and patch now. A fix is available for facade/ignition — see the affected versions and patch details below.

Unauthenticated remote code execution in Ignition

Also known asGHSA-4qwp-7c67-jmcc

Published

Jan 12, 2021

Updated

Oct 20, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

40 known

Exploitation data as of Oct 21, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-09-18 — including use in ransomware campaigns. Federal agencies were required to remediate by 2023-10-09.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2021-3129.

EPSS Exploitation Probability

via FIRST.org ↗

99.9%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2021-3129 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected

🐘facade/ignition🐘facade/ignition🐘facade/ignition🐘facade/ignition

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

Ignition before 2.5.2, as used in Laravel and other products, allows unauthenticated remote attackers to execute arbitrary code because of insecure usage of file_get_contents() and file_put_contents(). This is exploitable on sites using debug mode with Laravel before 8.4.2.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`facade/ignition`	≥ 2.5.0&&< 2.5.2	2.5.2`composer require facade/ignition:^2.5.2`
🐘Packagist	`facade/ignition`	≥ 2.0.0&&< 2.4.2	2.4.2`composer require facade/ignition:^2.4.2`
🐘Packagist	`facade/ignition`	≥ 1.7.0&&< 1.16.14	1.16.14`composer require facade/ignition:^1.16.14`
🐘Packagist	`facade/ignition`	all versions	1.6.15`composer require facade/ignition:^1.6.15`

Affected Products

1 product · 1 configurations

Application

ignitionfacade

< 2.5.2

range

Exploits & PoCs

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

EDB-49424webappsphp

Laravel 8.4.2 debug mode - Remote code execution

by SunCSR Team · Jan 14, 2021

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for facade/ignition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update facade/ignition to 2.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3129 is resolved across your whole dependency graph.
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.

How to detect CVE-2021-3129

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2021-3129 -u https://target

Template: Laravel with Ignition <= v8.4.2 Debug Mode - Remote Code Execution
Severity: critical
Impact: Successful exploitation of this vulnerability can lead to remote code execution, potentially allowing an attacker to take control of the affected system.
Remediation: Upgrade Laravel to version 8.4.3 or higher to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (z3bd, pdteam), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2021-3129 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weaponization

OpenSSF Scorecard

Package health score

ignition

3.2/10

Code-Review2/10

Maintained0/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

Jan 12, 2021

First exploit

Jan 14, 2021

1 day after disclosure — rapid exploitation

KEV added

Sep 18, 2023

Last updated

Oct 20, 2026

Identifiers

CVE-2021-3129

GHSA-4qwp-7c67-jmcc

References

Advisorynvd.nist.gov Fixgithub.com Webcisa.gov Webgithub.com Webgithub.com Packagegithub.com Evidencepacketstormsecurity.com Evidencepacketstormsecurity.com Evidenceambionics.io

Related vulnerabilities

This CVE is critical severity, in line with the other 2 CVEs affecting facade/ignition.

CVE-2021-43996CVE-2020-13909

Provenance

Sources

OSV.devNVDCISA KEVFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2021-3129 — ignition

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2021-3129

Frequently Asked Questions

Is CVE-2021-3129 in your dependencies?