CVE Intelligence
Skip to main content
CISA KEVRansomwarecriticalSSRFpublic exploit

CVE-2021-40438

CVE-2021-40438 — mod_proxy SSRF

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.

Published Updated Sources: NVD, Apache Software Foundation (CNA), CISA, FIRST EPSS, GitHub, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Dec 1, 2021

EPSS

100%

top of FIRST's scoreset

Affects

Apache

Apache HTTP Server

CVSS base

9

critical · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Apache HTTP Server to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply updates per vendor instructions.

Federal deadline Dec 15, 2021 — passed 1,754 days ago

Red Hat VEX · CVE-2021-40438

fixed532affected0not affected25

vendor_fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the updated pac…

vendor_fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.…

vendor_fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the updated pac…

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Treat as emergency remediation because CISA KEV status is present.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
ApacheApache HTTP ServerApache HTTP Server 2.4 to <= 2.4.48Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

High

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
9CVSS 3.1critical2.26NVD, CNA, Red Hat (VEX)
6.8CVSS 2.0medium8.66.4NVD

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-918 · Server-Side Request Forgery (SSRF)

  • Read Application Data
  • Execute Unauthorized Code or Commands::

Weakness & attack patterns

  • CWE-918Server-Side Request Forgery (SSRF)

Inferred from the weakness class — not observed against this CVE.

CAPEC-664 · Server Side Request Forgery

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

Listed

Dec 1, 2021

Federal deadline

Dec 15, 2021

passed 1,754 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

77

2 of the 5 sampled are weaponized

Exploit entries

17

Exploit-DB and CTI exploit indexes

Malware

Families a CTI source ties to this CVE. One named, with the total it tracks.

Families tracked

1

Named

Cobalt Strike

Cobalt Strike

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Prioritize edge telemetry for network-reachable Apache HTTP Server.
  • Monitor for scanner or exploit-pattern traffic after 94 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPScloud metadata access logsegress proxy logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

TeamTNTKinsingOperation Cobalt WhisperCobalt
  • ip91.210.242.1876

    AbuseIPDB Hourly Update · Aug 27, 2026

  • ip47.90.149.23812

    socks-proxy-Firehol · Jul 14, 2024

  • ip103.94.52.709

    KillNet-DDoS-Blocklist · Jul 20, 2023

  • ip196.1.93.1024

    Proxy · Jul 11, 2025

  • ip89.190.156.1278

    Maltiverse IP List · Dec 12, 2023

SOCRadar5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 9.0 (AV:N)

    Aug 6, 2026 · NVD

  3. 2025
  4. Cve is exploited n0m-d/CVE-2021-40438-POC

    Nov 9, 2025 · SOCRadar CTI

  5. Bulletin released on Mitre.

    Jul 28, 2025 · SOCRadar CTI

  6. Bulletin released on NIST.

    May 17, 2025 · SOCRadar CTI

  7. Bulletin released on Mitre.

    Feb 7, 2025 · SOCRadar CTI

  8. Bulletin released on NIST.

    Feb 7, 2025 · SOCRadar CTI

  9. 2024
  10. Bulletin released on NIST.

    Jul 24, 2024 · SOCRadar CTI

  11. 2023
  12. CVE is exploited. "Ostorlab/KEV"

    Dec 26, 2023 · SOCRadar CTI

  13. CVE is exploited. "sergiovks/CVE-2021-40438-Apache-2.4.48-SSRF-exploit"

    Dec 13, 2023 · SOCRadar CTI

  14. 2021
  15. Added to CISA KEV catalog

    Dec 1, 2021 · CISA

  16. Initial · CVE published

    Sep 16, 2021 · NVD

  17. Reported · 2.4.49 released

    Sep 16, 2021 · Apache Software Foundation

Source activity

Readings a source repeats on a schedule, counted rather than listed.

  • 8×Tweets · 1 times tweetedFeb 16, 2024 – Feb 1, 2025 · SOCRadar CTI
  • 6×Github ReposJan 26, 2024 – Nov 9, 2025 · SOCRadar CTI
  • 4×SVRS was changedDec 16, 2023 – Nov 29, 2025 · SOCRadar CTI
  • 3×ModifiedJul 24, 2024 – Feb 6, 2025 · SOCRadar CTI

References

30 on the record

Coverage

5 stories from the feeds we poll

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2021-40438 is mod_proxy SSRF, a critical vulnerability affecting Apache HTTP Server from Apache Software Foundation. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 94 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.