CVE-2026-73857

waiting for further signalsZero needs more public information before it can validate it.

GHSA-jx3r-phvx-2jmj ↗EUVD-2026-120508 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
owasp-modsecurity ModSecurity < 3.0.17
fixed in 3.0.17
CWE-787 Out-of-bounds Write
ETK-2026-3995Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 08h 30msince last run
27mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h39m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

ModSecurity 3.0.15 and 3.0.16 are affected when XML request-body parsing uses SecParseXmlIntoArgs set to On or OnlyArgs. An unauthenticated remote request can corrupt worker memory, potentially causing a worker crash, information exposure, or code execution.

mitigation

Upgrade ModSecurity to version 3.0.17. Until upgrades are complete, disable XML request-body parsing or avoid the affected SecParseXmlIntoArgs settings where operationally feasible.

fixed in 3.0.17

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
27m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 21:37Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-09 21:37Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-73857

{
  "etk_id": "ETK-2026-3995",
  "cve_id": "CVE-2026-73857",
  "display_id": "CVE-2026-73857",
  "ghsa_id": "GHSA-jx3r-phvx-2jmj",
  "euvd_id": "EUVD-2026-120508",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Uninitialized pointer memory corruption in ModSecurity XML parsing",
  "summary": "ModSecurity 3.0.15 and 3.0.16 are affected when XML request-body parsing uses SecParseXmlIntoArgs set to On or OnlyArgs. An unauthenticated remote request can corrupt worker memory, potentially causing a worker crash, information exposure, or code execution.",
  "mitigation": "Upgrade ModSecurity to version 3.0.17. Until upgrades are complete, disable XML request-body parsing or avoid the affected SecParseXmlIntoArgs settings where operationally feasible.",
  "vendor": "owasp-modsecurity",
  "product": "ModSecurity",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 3.0.17"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.0.17"
      ],
      "package_name": "libmodsecurity3",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 26.505910766666666,
  "t0_at": "2026-11-09T21:37:02.759000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T21:37:02.759000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T21:37:02.759000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-73857"
    }
  }
}

published 2026-11-09 21:48Z
last change 2026-11-11 03:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.