Threats / Apache / CVE-2021-40438
CVE-2021-40438
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Apache vulnerability
Apache HTTP Server mod_proxy can be manipulated via crafted request URI paths to forward requests to attacker-chosen origin servers, enabling request smuggling and server-side request forgery attacks.
Verdict
Today item — known-exploited.
Remote attackers can exploit mod_proxy request routing to redirect traffic to arbitrary servers, potentially accessing internal resources, bypassing security controls, or launching attacks against third-party systems. Active exploitation observed in the wild.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
515 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-12-01).
Probability (EPSS)
EPSS 0.99999 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apache, Apache. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-918 Server-Side Request Forgery (SSRF).CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious URI path that exploits mod_proxy's request forwarding logic to redirect the proxy to an origin server under my control.
Business
The organization's proxy infrastructure becomes an unwitting relay for attacker-controlled traffic, compromising request integrity and enabling lateral movement.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I use the compromised proxy to access internal backend services or resources that should be isolated from external networks.
Business
Internal systems and sensitive data become exposed through the proxy, violating network segmentation and data protection policies.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the proxy to launch attacks against third-party systems, masking my identity behind the organization's infrastructure.
Business
The organization faces legal liability, reputation damage, and potential sanctions for hosting attack infrastructure targeting external victims.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05