Skip to content
VulniPulse
Advisory severityMedium5.8Red Hat Linux

Medium [CVE-2026-52747] Security rule bypass due to incorrect handling of line breaks in form data

This medium-severity Red Hat Linux advisory covers CVE-2026-52747 affecting Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-52747 Source published Source updated

VulniPulse record published Record updated

CVE-2026-52747
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Summary

ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx.

Prior to 3.0.16, the multipart/form-data request body parser in libmodsecurity silently removes embedded line breaks from non-file form-field values before exporting them to ARGS and ARGS_POST because src/request_body_processor/multipart.cc overwrites reserved bytes in m_reserve instead of appending the current buffer.

This creates a parser differential between ModSecurity and backend applications that preserve line breaks in form fields, allowing rules that inspect ARGS or ARGS_POST to miss payloads whose dangerous syntax depends on a line break. This issue is fixed in version 3.0.16.

This bypass could lead to the execution of dangerous payloads that rely on line breaks, potentially resulting in a security compromise.

This issue is classified as Moderate severity primarily because: Conditions for Exploitation: Successful exploitation requires a specific scenario where the backend application preserves line breaks and is inherently vulnerable to a payload that utilizes those line breaks.

Additionally, the ModSecurity configuration must rely on rules inspecting the affected ARGS or ARGS_POST variables to allow the bypass to occur.

Is CVE-2026-52747 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-52747 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-52747?

Upgrade to a fixed release named by Red Hat:

  • 3.0.16

Confirm against the vendor advisory before you patch.

Affected versions
  • < 3.0.16

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Fixed versions
  • 3.0.16

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Mitigation checklist

Recommended fix / 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.

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Get an email when Red Hat RHEL & SELinux publishes the next one.

See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat RHEL & SELinux
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.