CVE-2021-41773

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild

Also known asEUVD-2021-28781 (ENISA EUVD) · GHSA-29h7-gr57-5f8r (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: >99.9%CVSS: 9.8Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

A flaw was found in a change made to path normalization in Apache HTTP Server 2.4.49. An attacker could use a path traversal attack to map URLs to files outside the directories configured by Alias-like directives. If files outside of these directories are not protected by the usual default configuration "require all denied", these requests can succeed. If CGI scripts are also enabled for these aliased pathes, this could allow for remote code execution. This issue is known to be exploited in the wild. This issue only affects Apache 2.4.49 and not earlier versions. The fix in Apache HTTP Server 2.4.50 was found to be incomplete, see CVE-2021-42013.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
>99.9%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
>99.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2021-41773

Published

October 5, 2021

Last Modified

February 17, 2026

Advisory Details (10)

Auto-updated Oct 30, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available.
Web page

oss-security - Re: CVE-2021-42013: Path Traversal and Remote Code Execution in Apache HTTP Server 2.4.49 and 2.4.50 (incomplete fix of CVE-2021-41773)

http://www.openwall.com/lists/oss-security/2021/10/08/3
Web page

oss-security - Re: CVE-2021-42013: Path Traversal and Remote Code Execution in Apache HTTP Server 2.4.49 and 2.4.50 (incomplete fix of CVE-2021-41773)

http://www.openwall.com/lists/oss-security/2021/10/08/2
Web page

oss-security - Re: CVE-2021-42013: Path Traversal and Remote Code Execution in Apache HTTP Server 2.4.49 and 2.4.50 (incomplete fix of CVE-2021-41773)

http://www.openwall.com/lists/oss-security/2021/10/08/1
Web page

oss-security - CVE-2021-42013: Path Traversal and Remote Code Execution in Apache HTTP Server 2.4.49 and 2.4.50 (incomplete fix of CVE-2021-41773)

http://www.openwall.com/lists/oss-security/2021/10/07/6
Web page

oss-security - RE: CVE-2021-41773: Path traversal and file disclosure vulnerability in Apache HTTP Server 2.4.49

http://www.openwall.com/lists/oss-security/2021/10/07/1
Web page

oss-security - CVE-2021-41773: Path traversal and file disclosure vulnerability in Apache HTTP Server 2.4.49

http://www.openwall.com/lists/oss-security/2021/10/05/2

Vendor Advisories for CVE-2021-41773(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(17 across 17 ecosystems)
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-r0: fixed in 2.4.50-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-1: fixed in 2.4.50-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-1: fixed in 2.4.50-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.50-1: fixed in 2.4.50-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 176× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,764 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,664 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 22:49 UTCEG score recompute
  2. 2026-11-01 22:49 UTCVendor advisory
  3. 2026-11-01 22:49 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-01 00:00 UTCEG score recompute
  5. 2026-11-01 00:00 UTCVendor advisory
  6. 2026-11-01 00:00 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-10-31 01:11 UTCEG score recompute
  8. 2026-10-31 01:11 UTCVendor advisory
  9. 2026-10-31 01:11 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-10-30 02:22 UTCEG score recompute
  11. 2026-10-30 02:22 UTCVendor advisory
  12. 2026-10-30 02:22 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-10-29 03:34 UTCEG score recompute
  14. 2026-10-29 03:33 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-10-28 04:45 UTCEG score recompute
  16. 2026-10-28 04:44 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  17. 2026-10-27 05:55 UTCEG score recompute
  18. 2026-10-27 05:55 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  19. 2026-10-26 07:04 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-10-25 18:21 UTCEG score recompute
  21. 2026-10-25 08:13 UTCEG score recompute
  22. 2026-10-25 08:13 UTCVendor advisory
  23. 2026-10-25 08:13 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  24. 2026-10-24 09:24 UTCEG score recompute
  25. 2026-10-24 09:24 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
Show 75 more
  1. 2026-10-23 10:35 UTCEG score recompute
  2. 2026-10-23 10:34 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-10-22 11:45 UTCEG score recompute
  4. 2026-10-22 11:44 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-10-21 12:55 UTCEG score recompute
  6. 2026-10-21 12:55 UTCVendor advisory
  7. 2026-10-21 12:55 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-10-20 14:07 UTCEG score recompute
  9. 2026-10-20 14:06 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-10-19 15:17 UTCEG score recompute
  11. 2026-10-19 15:17 UTCVendor advisory
  12. 2026-10-19 15:16 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-10-18 16:26 UTCVendor advisory
  14. 2026-10-18 16:26 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-10-18 08:53 UTCEG score recompute
  16. 2026-10-17 22:17 UTCEG score recompute
  17. 2026-10-17 22:17 UTCVendor advisory
  18. 2026-10-17 22:17 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  19. 2026-10-16 23:29 UTCEG score recompute
  20. 2026-10-16 23:28 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-10-16 00:39 UTCEG score recompute
  22. 2026-10-16 00:39 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-10-15 01:48 UTCEG score recompute
  24. 2026-10-15 01:48 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-10-14 16:29 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  26. 2026-10-14 02:59 UTCEG score recompute
  27. 2026-10-14 02:59 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  28. 2026-10-13 04:10 UTCVendor advisory
  29. 2026-10-13 04:10 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  30. 2026-10-12 19:09 UTCEG score recompute
  31. 2026-10-12 05:21 UTCVendor advisory
  32. 2026-10-12 05:21 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  33. 2026-10-12 01:38 UTCVendor advisory
  34. 2026-10-12 01:37 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  35. 2026-10-11 21:56 UTCEG score recompute
  36. 2026-10-11 21:56 UTCVendor advisory
  37. 2026-10-11 21:56 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  38. 2026-10-11 18:14 UTCEG score recompute
  39. 2026-10-11 18:14 UTCVendor advisory
  40. 2026-10-11 18:14 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  41. 2026-10-11 14:32 UTCEG score recompute
  42. 2026-10-11 14:32 UTCVendor advisory
  43. 2026-10-11 14:31 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  44. 2026-10-11 13:44 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  45. 2026-10-11 10:50 UTCVendor advisory
  46. 2026-10-11 10:50 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  47. 2026-10-11 07:07 UTCVendor advisory
  48. 2026-10-11 07:06 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  49. 2026-10-11 03:25 UTCVendor advisory
  50. 2026-10-11 03:25 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  51. 2026-10-10 23:42 UTCVendor advisory
  52. 2026-10-10 23:41 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  53. 2026-10-10 20:00 UTCVendor advisory
  54. 2026-10-10 20:00 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  55. 2026-10-10 16:17 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  56. 2026-10-10 12:36 UTCVendor advisory
  57. 2026-10-10 12:36 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  58. 2026-10-10 08:55 UTCVendor advisory
  59. 2026-10-10 08:55 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  60. 2026-10-10 05:13 UTCVendor advisory
  61. 2026-10-10 05:13 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  62. 2026-10-10 01:32 UTCVendor advisory
  63. 2026-10-10 01:32 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  64. 2026-10-09 21:49 UTCVendor advisory
  65. 2026-10-09 21:49 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  66. 2026-10-09 18:08 UTCVendor advisory
  67. 2026-10-09 18:07 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  68. 2026-10-09 14:23 UTCVendor advisory
  69. 2026-10-09 14:23 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  70. 2026-10-09 10:39 UTCVendor advisory
  71. 2026-10-09 10:38 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  72. 2026-10-09 06:50 UTCVendor advisory
  73. 2026-10-09 06:50 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5
  74. 2026-10-09 03:09 UTCVendor advisory
  75. 2026-10-09 03:09 UTCGHSA enrichmentGHSA-29h7-gr57-5f8r · GitHub severity HIGH · GitHub CVSS 7.5

Publicly available exploits

(16 references, 10 shown)

Public exploit code is referenced for this CVE (2 Metasploit modules, 2 Exploit-DB entries, 9 GitHub PoCs), as are 1 Nuclei detection template, 2 GitHub checker repositories. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-50512✓ verified
    Published Nov 11, 2021

    Apache HTTP Server 2.4.50 - Remote Code Execution (RCE) (3)

    Open source ↗
  • Metasploitauxiliary/scanner/http/apache_normalize_path✓ verified
    Published Oct 22, 2021

    Apache 2.4.49/2.4.50 Traversal RCE scanner

    Open source ↗
  • Metasploitexploit/multi/http/apache_normalize_path_rce✓ verified
    Published Oct 22, 2021

    Apache 2.4.49/2.4.50 Traversal RCE

    Open source ↗
  • Exploit-DBEDB-50383✓ verified
    Published Oct 6, 2021

    Apache HTTP Server 2.4.49 - Path Traversal & Remote Code Execution (RCE)

    Open source ↗
  • GitHub PoCthehackersbrain/CVE-2021-41773
    Published Mar 12, 2022

    Apache2 2.4.49 - LFI & RCE Exploit - CVE-2021-41773

    Open source ↗
  • GitHub checkerMrCl0wnLab/SimplesApachePathTraversal
    Published Oct 13, 2021

    Tool check: CVE-2021-41773, CVE-2021-42013, CVE-2020-17519

    Open source ↗
  • GitHub checkerim-hanzou/apachrot
    Published Oct 9, 2021

    Apache (Linux) CVE-2021-41773/2021-42013 Mass Vulnerability Checker

    Open source ↗
  • GitHub PoCinbug-team/CVE-2021-41773_CVE-2021-42013
    Published Oct 9, 2021

    CVE-2021-41773 CVE-2021-42013漏洞批量检测工具

    Open source ↗
  • GitHub PoCHightechSec/scarce-apache2
    Published Oct 7, 2021

    A framework for bug hunting or pentesting targeting websites that have CVE-2021-41773 Vulnerability in public

    Open source ↗
  • GitHub PoCjustakazh/mass_cve-2021-41773
    Published Oct 7, 2021

    MASS CVE-2021-41773

    Open source ↗

Frequently asked(6)

What is CVE-2021-41773?
CVE-2021-41773 is a critical-severity vulnerability; its CVE record was published on October 5, 2021. A flaw was found in a change made to path normalization in Apache HTTP Server 2.4.49. An attacker could use a path traversal attack to map URLs to files outside the directories configured by Alias-like directives. If files outside of these directories are not protected by the usual default…
When was the CVE record for CVE-2021-41773 published?
The CVE record for CVE-2021-41773 was published on October 5, 2021. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of February 17, 2026; the record at its source may have been updated since.
Is CVE-2021-41773 actively exploited?
Yes. CISA added CVE-2021-41773 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Apache HTTP Server. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2021-41773?
CVE-2021-41773 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2021-41773?
CVE-2021-41773 affects Apache HTTP Server. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2021-41773?
A fix for CVE-2021-41773 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-41773 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-41773

Explore →

Is Your Infrastructure Affected by CVE-2021-41773?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.