HTTP Response Splitting Vulnerability in Apache HTTP Server - CVE-2026-33523

apache2 Updated 05 May 2026

Summary

04/05/2026
N/A
No i
Medium
6.5

DEBIAN-CVE-2026-33523: HTTP response splitting vulnerability in multiple Apache HTTP Server modules with untrusted or compromised backend servers. Affects apache2 versions 2.4.48-3.1 – 2.4.66-8. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Apache HTTP Server is a widely used open-source web server software that enables users to serve web content. It is known for its flexibility, performance, and security features. However, certain modules within Apache HTTP Server are vulnerable to HTTP response splitting when interacting with untrusted or compromised backend servers. This vulnerability can lead to various security issues, including cache poisoning and cross-site scripting (XSS).

Vulnerability Detail

The vulnerability identified as CVE-2026-33523 is an HTTP response splitting issue that arises when Apache HTTP Server modules process responses from untrusted or compromised backend servers. This flaw can allow attackers to manipulate HTTP responses, potentially leading to cache poisoning, XSS attacks, and other malicious activities. The vulnerability affects versions of Apache HTTP Server up to 2.4.66, necessitating an upgrade to mitigate the risk.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can implement strict validation and sanitization of inputs from backend servers to minimize the risk of HTTP response splitting. However, upgrading to the patched version is the recommended solution.

Conclusion

CVE-2026-33523 represents a significant security risk for users of Apache HTTP Server versions up to 2.4.66. It is crucial for users to upgrade to version 2.4.67 or later to mitigate this vulnerability effectively. Regular monitoring and vulnerability management practices, such as using tools like Vulert, can help maintain the security of open-source software.

See every vulnerability recorded for apache2 →

Share this vulnerability

FAQ

CVE-2026-33523 is a vulnerability in Apache HTTP Server that allows for HTTP response splitting due to untrusted backend server responses.

The vulnerability affects Apache HTTP Server versions up to 2.4.66.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Potential risks include cache poisoning, cross-site scripting (XSS) attacks, and other malicious activities that can compromise user data and application integrity.

The CVSS score for CVE-2026-33523 is 6.5, indicating a medium level of severity.

Related vulnerabilities

Recent vulnerabilities recorded for apache2.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback