A crafted request uri-path can cause mod_proxy to forward the request to an origin server choosen by the remote user. This issue affects Apache HTTP Server 2.4.48 and earlier.
CVE-2021-40438
“—” beside the score: it is equal to NVD's CVSS score.
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-12-01), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.0 retained for reference. Confidence: HIGH.
- 843 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
- Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
- Linked to ransomware campaigns
A fix is available — apply it.
843 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2021-40438, in our KEV-Exposure radar’s Shodan-derived sample.
How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.
- CVSS v3
- 9.0
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 96EG Risk 96/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)Severity90% × 45%Impact severity (EG Severity): CVSS 9.0 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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- >99.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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: 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.
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-40438
Published
September 16, 2021
Last Modified
August 6, 2026
Advisory Details (10)
Auto-updated Oct 19, 2026[SECURITY] [DLA 2776-1] apache2 security update
https://lists.debian.org/debian-lts-announce/2021/10/msg00001.htmlPony Mail
https://lists.apache.org/thread.html/rf6954e60b1c8e480678ce3d02f61b8a788997785652e9557a3265c00%40%3Cusers.httpd.apache.org%3EPony Mail
https://lists.apache.org/thread.html/r82c077663f9759c7df5a6656f925b3ee4f55fcd33c889ba7cd687029%40%3Cusers.httpd.apache.org%3EPony Mail
https://lists.apache.org/thread.html/r82838efc5fa6fc4c73986399c9b71573589f78b31846aff5bd9b1697%40%3Cusers.httpd.apache.org%3EPony Mail
https://lists.apache.org/thread.html/r61fdbfc26ab170f4e6492ef3bd5197c20b862ce156e9d5a54d4b899c%40%3Cusers.httpd.apache.org%3EPony Mail
https://lists.apache.org/thread.html/r3925e167d5eb1c75def3750c155d753064e1d34a143028bb32910432%40%3Cusers.httpd.apache.org%3EPony Mail
https://lists.apache.org/thread.html/r2eb200ac1340f69aa22af61ab34780c531d110437910cb9c0ece3b37%40%3Cbugs.httpd.apache.org%3EPony Mail
https://lists.apache.org/thread.html/r210807d0bb55f4aa6fbe1512be6bcc4dacd64e84940429fba329967a%40%3Cusers.httpd.apache.org%3EApache HTTP Server 2.4 vulnerabilities - The Apache HTTP Server Project
https://httpd.apache.org/security/vulnerabilities_24.htmlVendor Advisories for CVE-2021-40438(8)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2021:3856Red Hat Product SecurityHigh
Red Hat Security Advisory: httpd security update
- RHSA-2021:3836Red Hat Product SecurityHigh
Red Hat Security Advisory: httpd:2.4 security update
- RHSA-2021:3837Red Hat Product SecurityHigh
Red Hat Security Advisory: httpd:2.4 security update
- RHSA-2021:3816Red Hat Product SecurityHigh
Red Hat Security Advisory: httpd:2.4 security update
- RHSA-2021:3754Red Hat Product SecurityHigh
Red Hat Security Advisory: httpd24-httpd security update
- RHSA-2021:3746Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.37 SP9 security update
- RHSA-2021:3745Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.37 SP9 security update
- CVE-2021-40438Microsoft Security Response Center (MSRC)Critical
mod_proxy SSRF
Patch Availability(9)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | apache2-bin (2.4.46-4ubuntu1.2) @ hirsute | 2026-10-23 | ubuntu |
| ubuntu | apache2-utils (2.4.18-2ubuntu3.17+esm2) @ xenial | 2026-10-23 | ubuntu |
| redhat | httpd-0:2.4.6-90.el7_7.1 | 2021-10-14 | redhat |
| redhat | httpd:2.4-8010020211008125020.c27ad7f8 | 2021-10-13 | redhat |
| redhat | httpd:2.4-8020020211008164029.4cda2c84 | 2021-10-13 | redhat |
| redhat | httpd:2.4-8040020211008164252.522a0ee4 | 2021-10-12 | redhat |
| redhat | httpd24-httpd-0:2.4.34-22.el7.1 | 2021-10-11 | redhat |
| redhat | jbcs-httpd24-mod_security-0:2.9.2-65.GA.jbcs.el7 | 2021-10-07 | redhat |
| redhat | patch | 2021-10-07 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(20 across 20 ecosystems)
Alpine:v3.11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.15(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.16(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.17(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.18(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.19(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | 2.4.38-3 ... 2.4.38-3+deb10u5 (6 versions) |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | 2.4.48-3.1 ... 2.4.51-1~bpo10+2 (15 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | 2.4.25-3 ... 2.4.25-3+deb9u9 (11 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 24× in last 7d / 260× 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,649 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,549 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 11:43 UTCEG score recompute
- 2026-10-23 11:43 UTCVendor advisory
- 2026-10-23 11:42 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-22 13:17 UTCEG score recompute
- 2026-10-22 13:17 UTCVendor advisory
- 2026-10-22 13:17 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-21 14:53 UTCVendor advisory
- 2026-10-21 14:53 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-20 16:29 UTCEG score recompute
- 2026-10-20 16:29 UTCVendor advisory
- 2026-10-20 16:29 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-19 18:04 UTCEG score recompute
- 2026-10-19 18:04 UTCVendor advisory
- 2026-10-19 18:04 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-18 19:39 UTCEG score recompute
- 2026-10-18 19:39 UTCVendor advisory
- 2026-10-18 19:39 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-18 08:54 UTCEG score recompute
- 2026-10-17 21:15 UTCEG score recompute
- 2026-10-17 21:15 UTCVendor advisory
- 2026-10-17 21:14 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-16 22:50 UTCEG score recompute
- 2026-10-16 22:50 UTCVendor advisory
- 2026-10-16 22:50 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-16 00:25 UTCEG score recompute
Show 75 moreShow fewer
- 2026-10-16 00:25 UTCVendor advisory
- 2026-10-16 00:24 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-15 01:59 UTCEG score recompute
- 2026-10-15 01:59 UTCVendor advisory
- 2026-10-15 01:59 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-14 03:35 UTCEG score recompute
- 2026-10-14 03:35 UTCVendor advisory
- 2026-10-14 03:34 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-13 05:09 UTCVendor advisory
- 2026-10-13 05:09 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-12 19:10 UTCEG score recompute
- 2026-10-12 06:44 UTCVendor advisory
- 2026-10-12 06:43 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-12 02:35 UTCVendor advisory
- 2026-10-12 02:35 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-11 22:27 UTCEG score recompute
- 2026-10-11 22:27 UTCVendor advisory
- 2026-10-11 22:27 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-11 18:21 UTCEG score recompute
- 2026-10-11 18:21 UTCVendor advisory
- 2026-10-11 18:21 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-11 14:15 UTCEG score recompute
- 2026-10-11 14:15 UTCVendor advisory
- 2026-10-11 14:15 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-11 10:09 UTCVendor advisory
- 2026-10-11 10:09 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-11 06:03 UTCVendor advisory
- 2026-10-11 06:03 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-11 01:57 UTCVendor advisory
- 2026-10-11 01:57 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-10 21:51 UTCVendor advisory
- 2026-10-10 21:51 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-10 17:45 UTCVendor advisory
- 2026-10-10 17:45 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-10 13:40 UTCVendor advisory
- 2026-10-10 13:39 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-10 09:33 UTCVendor advisory
- 2026-10-10 09:33 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-10 05:27 UTCVendor advisory
- 2026-10-10 05:27 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-10 01:20 UTCVendor advisory
- 2026-10-10 01:19 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-09 21:14 UTCVendor advisory
- 2026-10-09 21:14 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-09 17:07 UTCVendor advisory
- 2026-10-09 17:07 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-09 13:00 UTCVendor advisory
- 2026-10-09 13:00 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-09 08:54 UTCVendor advisory
- 2026-10-09 08:53 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-09 04:47 UTCVendor advisory
- 2026-10-09 04:46 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-09 00:40 UTCVendor advisory
- 2026-10-09 00:40 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-08 20:34 UTCVendor advisory
- 2026-10-08 20:34 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-08 16:28 UTCVendor advisory
- 2026-10-08 16:28 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-08 12:20 UTCVendor advisory
- 2026-10-08 12:20 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-08 08:14 UTCVendor advisory
- 2026-10-08 08:13 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-08 04:08 UTCVendor advisory
- 2026-10-08 04:07 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-08 00:01 UTCVendor advisory
- 2026-10-08 00:01 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-07 19:55 UTCVendor advisory
- 2026-10-07 19:55 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-07 15:49 UTCVendor advisory
- 2026-10-07 15:49 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-07 11:42 UTCVendor advisory
- 2026-10-07 11:42 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-07 07:36 UTCVendor advisory
- 2026-10-07 07:36 UTCGHSA enrichmentGHSA-rwxq-58vm-3v2j · GitHub severity CRITICAL · GitHub CVSS 9.0
- 2026-10-07 03:30 UTCVendor advisory
Publicly available exploits
(6 references)Public exploit code is referenced for this CVE (5 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.
- GitHub PoCsergiovks/CVE-2021-40438-Apache-2.4.48-SSRF-exploitPublished Dec 12, 2023
CVE-2021-40438 Apache <= 2.4.48 SSRF exploit
Open source ↗ - GitHub PoCKashkovsky/CVE-2021-40438Published Apr 3, 2022
Apache forward request CVE
Open source ↗ - Open source ↗GitHub PoCBabyTeam1024/CVE-2021-40438Published Oct 28, 2021
- GitHub PoCsixpacksecurity/CVE-2021-40438Published Oct 24, 2021
CVE-2021-40438 exploit PoC with Docker setup.
Open source ↗ - Open source ↗GitHub PoCxiaojiangxl/CVE-2021-40438Published Oct 18, 2021
- Nucleihttp/cves/2021/CVE-2021-40438.yamlPublished Oct 14, 2021
Apache <= 2.4.48 Mod_Proxy - Server-Side Request Forgery
Open source ↗
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:10:apache2
- CVE-2021-39275EG 9.8EPSS p99CRITICAL
- CVE-2021-26691EG 9.8EPSS p99CRITICAL
- CVE-2019-10082EG 9.1EPSS p97CRITICAL
- CVE-2019-10092NVD 6.1EG 8.8EPSS p100HIGH
- CVE-2021-26690NVD 7.5EG 8.5EPSS p99HIGH
- CVE-2021-34798NVD 7.5EG 8.4EPSS p99HIGH
- CVE-2019-10098NVD 6.1EG 8.4EPSS p99HIGH
- CVE-2021-31618NVD 7.5EG 8.1EPSS p99HIGH
- CVE-2020-35452NVD 7.3EG 8.1EPSS p99HIGH
- CVE-2020-1927NVD 6.1EG 7.5EPSS p99HIGH
Same vendor
5 shownubuntu:USN-5090-1 · redhat:RHSA-2021:3816
Frequently asked(6)
What is CVE-2021-40438?
When was the CVE record for CVE-2021-40438 published?
Is CVE-2021-40438 actively exploited?
What is the CVSS score of CVE-2021-40438?
Which products are affected by CVE-2021-40438?
How do I remediate CVE-2021-40438?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-40438
Is Your Infrastructure Affected by CVE-2021-40438?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.