
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-73857 is an uninitialized pointer dereference vulnerability in the ModSecurity v3 XML request body processor, classified as "ModSecurity v3 XML Request Body Processor Uninitialized Pointer Dereference Vulnerability." It affects ModSecurity versions 3.0.15 and 3.0.16 (the vulnerable code path was introduced in v3.0.15); earlier 3.0.x releases and ModSecurity 2.x are not affected. The vulnerability was reported by Tobias Klein (tk@trapkit.de), disclosed via GitHub Security Advisory GHSA-jx3r-phvx-2jmj on September 30, 2026, and published to NVD on November 9, 2026. It carries a CVSS v3.1 base score of 7.5 (High) (GitHub Advisory, Feedly).
The root cause is an uninitialized pointer access (CWE-824) combined with an out-of-bounds write (CWE-787) in the XML-into-ARGS SAX end-element callback within src/request_body_processor/xml.cc. When SecParseXmlIntoArgs is set to On or OnlyArgs, the XMLNodes::parsing_ctx_arg member is not initialized before the SAX end-element callback can reference it; if the SecArgumentsLimit is hit during XML parsing, the callback calls xmlStopParser(xml_data->parsing_ctx_arg) on the uninitialized pointer, resulting in a constant-value write to an attacker-controlled address. The fix initializes parsing_ctx_arg to NULL in the constructor and adds a NULL check before calling xmlStopParser, and also ensures the pointer is set during processChunk before the SAX callbacks can fire (GitHub Advisory, GitHub Commit). The vulnerability is only reachable when SecParseXmlIntoArgs is explicitly enabled (it is Off by default) (GitHub Advisory).
A remote, unauthenticated attacker can send a single crafted HTTP POST request with an XML body to a server running a vulnerable ModSecurity configuration, triggering memory corruption in the web server worker process. The impact ranges from denial of service (worker process crash/termination) to potential memory disclosure and execution-flow redirection, which could lead to remote code execution in the worst case. The CVSS score reflects a confirmed high availability impact; confidentiality and integrity impacts are rated None in the base score but are noted as possible in more severe exploitation scenarios (GitHub Advisory, Feedly).
No public proof-of-concept exploit code or in-the-wild exploitation has been reported for CVE-2026-73857 as of the latest available data. The EPSS score is approximately 0.40%, indicating a low probability of exploitation in the near term. The vulnerability is automatable (no user interaction or privileges required), but exploitation is gated by the non-default SecParseXmlIntoArgs On or OnlyArgs configuration. The CVE status is listed as "Deferred" and it does not appear in the CISA Known Exploited Vulnerabilities catalog (Feedly, GitHub Advisory).
SecParseXmlIntoArgs set to On or OnlyArgs. This can be done via banner analysis, error responses, or configuration leaks.Content-Type: text/xml (or trigger the XML body processor via a rule) containing an XML body with more elements than the server's SecArgumentsLimit allows (e.g., many <node> elements exceeding the default argument limit).xmlStopParser() with the uninitialized parsing_ctx_arg pointer, causing a write of a constant value to an attacker-influenced address.Content-Type: text/xml headers containing large numbers of XML elements targeting web applications protected by ModSecurity; repeated requests from the same source IP causing worker crashes.SecArgumentsLimit.httpd child processes, Nginx worker processes) following receipt of XML POST requests.Upgrade ModSecurity to version 3.0.17, which contains the fix for this vulnerability (GitHub Release). As an immediate workaround for deployments that cannot upgrade, ensure SecParseXmlIntoArgs is set to Off (which is the default value) in the ModSecurity configuration — this prevents the vulnerable code path from being reached entirely (GitHub Advisory). ModSecurity 2.x and ModSecurity 3.x versions prior to 3.0.15 are not affected and do not require remediation for this specific issue.
The vulnerability received coverage from multiple security news outlets including CyberSecurityNews, CyberPress, and The Hacker News (in weekly recap roundups), reflecting moderate community interest (Feedly). Security researchers noted that while the vulnerability is technically severe due to its potential for memory corruption and possible RCE, the non-default configuration requirement (SecParseXmlIntoArgs On) significantly limits the real-world attack surface. The fix was credited to researcher Tobias Klein of trapkit.de, a well-known security researcher, lending credibility to the severity assessment (GitHub Advisory).
Fix availability across major Linux distributions and their releases.
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."