CVE-2021-43996: The Ignition component before 1.16.15, and 2.0.x before 2.0.6, for Laravel has a "fix variable names" feature

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2021-43996 is a critical-severity flaw (CVSS 9.8) affecting ignition. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Ignition component before 1.16.15, and 2.0.x before 2.0.6, for Laravel has a "fix variable names" feature that can lead to incorrect access control.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.7% (top 22%)
CISA exploited list	No
Published	2021-11-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: facade

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

Am I affected?

Timeline

2021-11-17 20:15 UTCPublished CVE record published
2026-06-17 04:11 UTCUpdated Record last modified

facade ignition UPGRADE

Affected: < 1.6.15 · >= 2.0.0 and < 2.0.6

Fixed in: 1.6.15, 2.0.6

Safe to downgrade to: a release before 2.0.0

1. Check installed version

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

2. UPGRADE to 1.6.15 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ignition

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison ignition sudo apt install ignition=<VERSION_BEFORE_2.0.0> sudo apt-mark hold ignition

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ignition sudo dnf downgrade ignition-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add ignition

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2021-43996?

ignition: upgrade to 1.6.15, 2.0.6. Exact commands for each OS are on this page.

Is CVE-2021-43996 being exploited?

CVE-2021-43996 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-2021-43996 affect?

CVE-2021-43996 affects ignition. Severity is critical (CVSS 9.8). The Ignition component before 1.16.15, and 2.0.x before 2.0.6, for Laravel has a "fix variable names" feature that can lead to incorrect access control.

How urgent is CVE-2021-43996?

Priority 59/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Laravel vulnerabilities

Related CVEs

CVE-2025-13913 MEDIUM 6.3 UPGRADE A privileged Ignition user, intentionally or otherwise, imports an external file with a specially crafted payl
CVE-2023-50233 HIGH 8.8 UPGRADE Inductive Automation Ignition getJavaExecutable Directory Traversal Remote Code Execution Vulnerability
CVE-2023-50232 HIGH 8.8 UPGRADE Inductive Automation Ignition getParams Argument Injection Remote Code Execution Vulnerability
CVE-2023-50223 HIGH 8.8 UPGRADE Inductive Automation Ignition ExtendedDocumentCodec Deserialization of Untrusted Data Remote Code Execution Vu
CVE-2023-50222 HIGH 8.8 UPGRADE Inductive Automation Ignition ResponseParser Notification Deserialization of Untrusted Data Remote Code Execut

References

← Back to latest CVEs