What is CVE-2024-38475?
Improper escaping of output in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows an attacker to map URLs to filesystem locations that are permitted to be served by the server but are not intentionally/directly reachable by any URL, resulting in code execution or source code disclosure. Substitutions in server context that use a backreferences or variables as the first segment of the substitution are affected. Some unsafe RewiteRules will be broken by this change and the rewrite flag "UnsafePrefixStat" can be used to opt back in once ensuring the substitution is appropriately constrained.
The record classifies CVE-2024-38475 under weakness class CWE-116. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 838 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 9.1 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - EPSS (FIRST)
- 99.9% probability of exploitation in the next 30 days, higher than 99.9% of all scored CVEs
- CISA KEV
- Listed since 2025-05-01, federal remediation deadline 2025-05-22
- Threadlinqs priority
- 9/10 — CISA KEV-listed, which Threadlinqs floors at 9
- Published
- 2024-07-01, last modified 2025-11-03
Is CVE-2024-38475 being exploited?
CISA added CVE-2024-38475 to the Known Exploited Vulnerabilities catalog on 2025-05-01, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2025-05-22 under BOD 22-01. Weaponised exploit code for CVE-2024-38475 is publicly available. 6 public proof-of-concept repositories are tracked for this identifier. A ProjectDiscovery Nuclei detection template exists (http/cves/2024/CVE-2024-38475.yaml). It currently carries a trending score of 50 in the Threadlinqs vulnerability feed.
- p0in7s/CVE-2024-38475 (github)
- soltanali0/CVE-2024-38475 (github)
- abrewer251/CVE-2024-38475_SonicBoom_Apache_URL_Traversal_PoC (github)
- syaifulandy/CVE-2024-38475 (github)
- Nyakki-Labs-0x420/Myesve (github)
- trickest/cve (trickest)
Affected products and versions
- Apache Software Foundation: Apache HTTP Server
How to fix CVE-2024-38475
The record marks a vendor fix as available for CVE-2024-38475. Patch reference: https://github.com/apache/httpd/commit/9a6157d1e2f7ab15963020381054b48782bc18cf. Vendor advisory: https://httpd.apache.org/security/vulnerabilities_24.html. Because CVE-2024-38475 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2025-05-22. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2024-38475
1 tracked threat in the Threadlinqs corpus references CVE-2024-38475, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, NVD, FIRST EPSS, CISA KEV, GitHub Security Advisories, public proof-of-concept repositories, ProjectDiscovery Nuclei. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.