CVE-2026-33523·Apache vulnerability
HTTP response splitting vulnerability in multiple Apache HTTP Server modules with untrusted or compromised backend servers. This issue affects Apache HTTP Server: from through 2.4.66. Users are recommended to upgrade to version 2.4.67, which fixes the issue.
- Severity
- medium
- Software
- Apache
- Fixed in
- 2.4.67
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.44% — higher than 36% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 2.4.0
Until: 2.4.67
Fixed in: 2.4.67
How to fix this CVE
Upgrade Apache HTTP Server to version 2.4.67 or later to mitigate this HTTP response splitting vulnerability that can occur when backend servers are untrusted or compromised. Review your proxy and module configurations to ensure strict validation of upstream responses. If immediate patching is not possible, disable or restrict access to affected backend servers until the update can be applied.
sudo dnf update httpdDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
POST|GET.*HTTP/1\.[01]\r\nHost:.*\r\n.*\r\n\r\nHTTP/1\.[01]|Suspicious double HTTP headers in proxy response logs containing injected status lines or header sequencesWAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
Configure WAF rules to validate and sanitize backend HTTP responses before forwarding to clients. Block responses containing unexpected HTTP/1.x status lines within the body or header injection patterns. Implement strict Content-Length validation and reject responses with mismatched lengths.How to check if you are affected
- Run `apache2 -v` (Ubuntu/Debian) or `httpd -v` (RHEL/CentOS) to check the installed Apache version. Versions 2.4.0 through 2.4.66 are vulnerable.
- Verify which Apache modules are loaded by examining `apache2ctl -M` or `httpctl -M` and confirm if mod_proxy, mod_proxy_http, or similar backend-routing modules are active.
- Search Apache access and error logs for malformed or suspicious response headers using: `grep -E '(\r\n|HTTP/1\.[01].*\r\n)' /var/log/apache2/error.log | head -20`
- After patching, re-run `apache2 -v` or `httpd -v` and confirm the version is 2.4.67 or higher, then restart Apache with `sudo systemctl restart apache2` or `sudo systemctl restart httpd`.
FAQ
What is CVE-2026-33523?
This vulnerability allows HTTP response splitting attacks when Apache communicates with untrusted or compromised backend servers. An attacker controlling a backend server can inject additional HTTP headers or responses into the client response stream, potentially leading to cache poisoning, session hijacking, or information disclosure.
Is CVE-2026-33523 being actively exploited?
No, CVE-2026-33523 is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and there are no public exploits available. However, the attack requires compromised or untrusted backend infrastructure, which limits widespread exploitation.
What versions of Apache are affected by CVE-2026-33523?
Apache HTTP Server versions 2.4.0 through 2.4.66 are vulnerable. The fix is available in version 2.4.67 and later.
How do I check if my server is vulnerable to CVE-2026-33523?
Run `apache2 -v` or `httpd -v` on your server. If the version is 2.4.66 or earlier, you are vulnerable. Additionally, verify that proxy modules are enabled with `apache2ctl -M | grep proxy`.
Does Defensia detect CVE-2026-33523?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Apache is installed on a monitored server, CVE-2026-33523 will appear in your dashboard with remediation steps.
Related Apache CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-33523. Free for 1 server.
Get started free