Skip to main content
Vulnerability Database/CVE-2026-114457

CVE-2026-114457: mod_qos JSON Body Filtering DoS Vulnerability

CVE-2026-114457 is a denial of service flaw in mod_qos that allows unauthenticated attackers to crash Apache worker processes via malformed JSON requests. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-114457 Overview

CVE-2026-114457 is a Denial of Service (DoS) vulnerability in mod_qos, a Quality of Service module for the Apache HTTP Server. An unauthenticated remote attacker can crash an Apache worker process by sending a specially crafted JSON request when JSON body filtering is enabled. The underlying weakness is an improper null termination [CWE-170] during processing of percent-encoded input, which causes the module to read past allocated memory boundaries. The flaw affects availability only and does not expose data confidentiality or integrity.

Critical Impact

Unauthenticated remote attackers can trigger Apache worker process crashes on servers running mod_qos with JSON body filtering enabled, degrading service availability.

Affected Products

  • Apache HTTP Server deployments using the mod_qos module
  • Configurations with JSON body filtering enabled in mod_qos
  • Red Hat distributions packaging mod_qos (see Red Hat CVE-2026-114457 Advisory)

Discovery Timeline

  • 2026-10-22 - CVE CVE-2026-114457 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-114457

Vulnerability Analysis

The vulnerability resides in the JSON body filtering code path of mod_qos. When the module decodes percent-encoded sequences inside a JSON payload, it fails to correctly terminate the resulting string. Subsequent string operations then read beyond the allocated buffer, resulting in an out-of-bounds read. The invalid memory access causes the Apache worker process handling the request to crash. Repeated requests can exhaust worker capacity and interrupt service for legitimate clients. Exploitation requires no authentication and no user interaction, but attack complexity is elevated because the server must be configured with JSON body filtering enabled.

Root Cause

The root cause is an improper null termination weakness [CWE-170] in the percent-decoding routine used during JSON body inspection. The decoded string is not reliably null-terminated, so downstream string-handling functions traverse memory until they encounter an unrelated null byte or hit an unmapped page.

Attack Vector

The attack vector is network-based. An attacker sends a crafted HTTP request with a JSON body containing malformed percent-encoded sequences to any resource processed by mod_qos with JSON filtering active. The targeted worker process crashes while parsing the request, producing a DoS condition that recurs for each malicious request.

No verified public exploit code is available. See the Red Hat Bug 2558311 Details for additional technical context.

Detection Methods for CVE-2026-114457

Indicators of Compromise

  • Unexpected Apache worker process crashes or segmentation faults correlated with inbound HTTP requests containing JSON bodies.
  • Core dumps or mpm error log entries referencing mod_qos frames during request processing.
  • Elevated rates of HTTP 5xx responses on endpoints that accept JSON input.

Detection Strategies

  • Inspect Apache error_log for repeated worker termination messages such as child pid ... exit signal Segmentation fault.
  • Alert on anomalous volumes of inbound requests carrying JSON bodies with heavy percent-encoding, especially from a single source.
  • Correlate worker crash events with specific client IPs and URIs to identify repeatable crash triggers.

Monitoring Recommendations

  • Monitor Apache process health metrics and the rate of worker respawns via your observability stack.
  • Enable detailed access logging that captures request body size and Content-Type to support post-incident triage.
  • Forward web server logs to a centralized analytics platform to surface crash patterns across the fleet.

How to Mitigate CVE-2026-114457

Immediate Actions Required

  • Identify all Apache servers running mod_qos and determine whether JSON body filtering directives are enabled.
  • Apply vendor-supplied updates for mod_qos as soon as fixed packages are published by your distribution.
  • Where immediate patching is not possible, disable JSON body filtering in mod_qos configuration to remove the vulnerable code path.

Patch Information

Consult the Red Hat CVE-2026-114457 Advisory and Red Hat Bug 2558311 Details for authoritative package versions and errata. Install updated mod_qos builds from your distribution and restart the Apache HTTP Server to activate the fix.

Workarounds

  • Disable mod_qos JSON body filtering directives until a patched module is deployed.
  • Place a reverse proxy or Web Application Firewall (WAF) in front of Apache to reject or normalize malformed percent-encoded JSON payloads.
  • Enforce request rate limiting on endpoints that accept JSON to reduce the impact of repeated crash attempts.
bash
# Example: disable mod_qos JSON body filtering in Apache configuration
# Comment out or remove any QS_SetEnvIfBody / JSON filter directives,
# then restart Apache.
# sudo sed -i 's/^\(\s*QS_SetEnvIfBody.*\)/# \1/' /etc/httpd/conf.d/mod_qos.conf
# sudo systemctl restart httpd

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.