CVE-2026-73856

Description

A flaw was found in ModSecurity, which can lead to information disclosure. The web application firewall evaluates HTTP response Content-Type headers case-sensitively against configured rules, causing mixed-case media types to bypass response body inspection. An unauthenticated remote attacker can exploit this issue to receive restricted server responses that would otherwise be blocked, potentially exposing sensitive error or debug data.

Statement

Red Hat rates this vulnerability as Important because an unauthenticated remote attacker can completely circumvent outbound web application firewall filtering without requiring privileges or user interaction. This elevated severity reflects the ability to bypass defensive inspection boundaries over the network, allowing confidential server data to leak to unauthorized clients. Deployments utilizing ModSecurity to intercept outbound response payloads are directly exposed whenever backend web services emit mixed-case MIME headers. Environments where response body analysis is not utilized or where backend servers consistently emit strictly lowercase media headers face lower operational exposure.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

--- CME Mitigation Guidance (2026-11-06) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to normalize response Content-Type header values to lowercase prior to evaluating against SecResponseBodyMimeType inspection sets: upgrade to ModSecurity 3.0.17, which convert the response Content-Type value to lowercase using utils::string::tolower before querying the configured MIME type set, closing mixed-case Content-Type response headers. Until patched, this is a concern on deployments running ModSecurity v3 (3.0.0 to 3.0.16) configured with phase 4 response body inspection rules, so ensure backend web servers consistently emit strictly lowercase Content-Type headers to prevent skipping response body inspection. These controls limit blast radius and contain exploitation, but they do not fix the underlying case-sensitive Content-Type matching defect — apply the upstream patch to fully remediate.

Understanding the Weakness (CWE)

Access Control

Technical Impact: Bypass Protection Mechanism

Improperly handled case sensitive data can lead to several possible consequences, including: - case-insensitive passwords reducing the size of the key space, making brute force attacks easier - bypassing filters or access controls using alternate names - multiple interpretation errors using alternate names.

Frequently Asked Questions

Want to get errata notifications? Sign up here.