# CVE-2026-73857 — owasp-modsecurity ModSecurity

> As of 2026-11-09, CVE-2026-73857 is a HIGH-severity vulnerability in owasp-modsecurity ModSecurity, CVSS v3.1 7.5. Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-73857, most recently “ModSecurity WAF Vulnerabilities: Multipart filename* Upload Bypass (CVE-2026-104269) and XML Body Processor Uninitialized Pointer Dereference (CVE-2026-73857)”.

**Last updated:** 2026-11-09

## What is CVE-2026-73857?

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.

The record classifies CVE-2026-73857 under weakness classes [CWE-787](https://intel.threadlinqs.com/cwe/CWE-787), [CWE-824](https://cwe.mitre.org/data/definitions/824.html). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 7.5 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-09

## Is CVE-2026-73857 being exploited?

It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **owasp-modsecurity**: ModSecurity

## How to fix CVE-2026-73857

No vendor patch reference has been recorded for CVE-2026-73857 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-73857

1 tracked threat in the Threadlinqs corpus references CVE-2026-73857, either in the campaign’s CVE list or as an indicator on the campaign record.

- [ModSecurity WAF Vulnerabilities: Multipart filename* Upload Bypass (CVE-2026-104269) and XML Body Processor Uninitialized Pointer Dereference (CVE-2026-73857)](https://intel.threadlinqs.com/threat/TL-2026-5550) — HIGH · 2026-11-09

## Sources

Enriched from CVE.org.

**Vendor advisory and patch**

- [github.com](https://github.com/owasp-modsecurity/ModSecurity/security/advisories/GHSA-jx3r-phvx-2jmj)

**Other references**

- [github.com](https://github.com/owasp-modsecurity/ModSecurity/commit/e979a73e89d60cefdf42b41bb38bf1e456d7909f)
- [github.com (v3.0)](https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v3.0.17)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-73857
Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Sign up free (Blue): https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
