CVE-2021-42013: Path Traversal and Remote Code Execution in Apache HTTP Server 2.4.49 and 2.4.50
- Vendors
- Apache Software FoundationNetAppFedora ProjectOracle Corporation
CVE-2021-42013 is a path traversal vulnerability in Apache HTTP Server 2.4.49 and 2.4.50 associated with the incomplete fix for CVE-2021-41773. Crafted URL paths, including double-encoded traversal sequences, bypass path normalization restrictions and map requests to files outside directories configured by Alias-like directives. File access succeeds when the target resources are not protected by the default "Require all denied" configuration. If CGI execution is enabled for the affected aliased paths, exploitation can also permit remote code execution. Versions earlier than 2.4.49 are not affected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can disclose files outside the intended served directories, subject to Apache authorization rules and operating-system permissions. With CGI enabled and permissive access controls, an attacker can execute arbitrary commands with the privileges of the server's CGI execution context, compromising the confidentiality, integrity, and availability of accessible resources. Exploitation has been used for cryptomining malware deployment and botnet propagation, including Zerobot and Enemybot.
Mitigation
If you can’t patch tonight, do this now.
Enforce "Require all denied" for filesystem locations outside explicitly authorized served directories, and review Alias-like directives and authorization overrides for unintended access. Disable CGI execution on affected aliased paths where it is unnecessary; this reduces the remote-code-execution risk but does not independently eliminate file disclosure. Restrict network exposure and deploy WAF or IPS virtual-patching rules that recognize encoded and double-encoded traversal attempts while permanent updates are prepared.
Remediation
Patch, then assume compromise.
Apply the vendor fixes for CVE-2021-42013 by upgrading affected Apache HTTP Server installations to a supported, patched release. Apache HTTP Server 2.4.50 is not an adequate remediation because its fix for CVE-2021-41773 was incomplete. Update affected bundled Apache components through the relevant product vendor's security updates.
Exploits
28 exploits validated by Mallory's analysis. Hidden: 11 rejected by Mallory's analysis as not a working exploit; 3 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2021-42013 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
- Is there a public exploit for CVE-2021-42013?
- Yes. Mallory tracks 28 public exploits or proofs of concept for CVE-2021-42013, the earliest disclosed May 10, 2021.
- Is there a patch for CVE-2021-42013?
- Apply the vendor fixes for CVE-2021-42013 by upgrading affected Apache HTTP Server installations to a supported, patched release. Apache HTTP Server 2.4.50 is not an adequate remediation because its fix for CVE-2021-41773 was incomplete.
- What products are affected by CVE-2021-42013?
- Apache Software Foundation Apache HTTP Server, NetApp Cloud Backup, Fedora Project Fedora, Oracle Corporation Instantis Enterprisetrack, Oracle Corporation JD Edwards EnterpriseOne Tools, and 1 more.
- How severe is CVE-2021-42013?
- CVE-2021-42013 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 100.0% (100th percentile) as of Oct 16, 2026.
Recent activity
25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.