Read the docs

Uninitialized pointer use in ModSecurity XML request body parser

Priority LOW 39CWE-787Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-787 and the CVSS impact.

Summary

ModSecurity from 3.0.15 before 3.0.17 is affected when XML request body processing is set to On or OnlyArgs. A parsing context pointer can stay uninitialized in the SAX end-element callback and then be dereferenced (CWE-824). A single unauthenticated crafted HTTP request can make a worker write a constant value to an attacker-controlled address, which can terminate the worker, disclose memory or redirect execution.

Written with Claude Haiku 5.5 from the sources below · 2026-11-14

Description from the CNA

ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. From 3.0.15 until 3.0.17, XML request body processing with SecParseXmlIntoArgs set to On or OnlyArgs can leave XMLNodes::parsing_ctx_arg uninitialized in the SAX end-element callback. A single crafted unauthenticated HTTP request can make a worker dereference the pointer, resulting in a constant-value write to an attacker-controlled address. The resulting memory corruption can terminate the worker and may disclose memory or redirect execution. Earlier 3.0.x releases and ModSecurity 2.x do not use the affected path. This issue is fixed in version 3.0.17.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00402 35th percentileScored 2026-11-16
Fix Fixed ModSecurity (owasp-modsecurity): 3.0.17

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
owasp-modsecurityModSecurity3.0.15 to before 3.0.173.0.17Patch availableCNA
  • ModSecurity Vendorowasp-modsecurity Affected 3.0.15 to before 3.0.17 Fixed in 3.0.17 Patch available CNA

Remediation

Update ModSecurity to version 3.0.17, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-14

  • Fix · CNA ModSecurity (owasp-modsecurity) Fixed in 3.0.17

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-11-09 Threatist record created from CVE-2026-73857
  2. 2026-11-10 CISA SSVC decision points changed
  3. 2026-11-10 Priority changed: MEDIUM → LOW
  4. 2026-11-14 Affected versions changed · Red Hat
  5. 2026-11-14 CVSS score added · Red Hat

References

  • TI-2026-85491 ModSecurity filename* parsing lets uploads bypass multipart rules CVSS 3.1HIGH 8.6
  • TI-2026-85489 ModSecurity skips response body inspection for mixed-case types CVSS 3.1HIGH 8.6
  • TI-2026-37865 ModSecurity: Multipart form-data parser silently strips embedded line breaks from… CVSS 3.1HIGH 8.6
  • TI-2025-40548 FACTION Unauthenticated Custom Extension Upload leads to RCE CVSS 3.1CRITICAL 9.8
  • TI-2022-07517 Path Traversal in ESAPI CVSS 3.1CRITICAL 9.8
  • TI-2026-30581 ModSecurity: Unsigned integer underflow in @verifySSN / @verifyCPF / @verifySVNR operators CVSS 4.0HIGH 8.2
See all 59 →

Sources