CVE-2024-42516 | Apache HTTP Server: HTTP response splitting

HTTP response splitting in the core of Apache HTTP Server allows an attacker who can manipulate the Content-Type response headers of applications hosted or proxied by the server can split the HTTP response. This vulnerability was described as CVE-2023-38709 but the patch included in Apache HTTP Server 2.4.59 did not address the issue. Users are recommended to upgrade to version 2.4.64, which fixes this issue.

Published: 2025-07-10 Last update: 2025-11-04 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-42516 is rated Moderate Risk (55.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.70%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-42516

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-03 0.92% 0.70% -0.21%
2 2026-05-06 0.32% 0.92% +0.59%
3 2026-02-21 — 0.32% —

Full EPSS history (22 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-42516

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-42516

OS Trackers for CVE-2024-42516

vendor priority summary link
alpine — CVE-2024-42516: 1 source package rows (apache2); 5 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 5, open 0. https://security.alpinelinux.org/vuln/CVE-2024-42516
debian not yet assigned CVE-2024-42516 not yet assigned priority: Debian including 1 source packages (apache2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-42516
redhat medium — https://access.redhat.com/security/cve/CVE-2024-42516
suse medium — https://www.suse.com/security/cve/CVE-2024-42516/
ubuntu medium CVE-2024-42516 medium priority: Ubuntu including 1 source packages (apache2), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): released 8, needs-triage 1. https://ubuntu.com/security/CVE-2024-42516

Affected software / configurations for CVE-2024-42516

Vendor Product Version Raw CPE
apache http_server >= 2.4.0, < 2.4.64 cpe:2.3:a:apache:http_server:*:*:*:*:*:*:*:*

References for CVE-2024-42516

cvelogic Threat Intelligence