---
schema: 1
kind: vulnerability
title: "CVE-2026-131914, Idunno.AntiCsrf 0.9.1 and earlier, a defunct anti-CSRF module for ASP.NET WebForms: one unauthenticated POST with a crafted CSRF form field is deserialized without validation and runs code in the IIS worker process; Mandiant observed exploitation in the wild and no patch exists, so the module has to be removed (CVSS 4.0 9.3)"
headline: "Idunno.AntiCsrf (ASP.NET WebForms) unauthenticated deserialization RCE exploited, no patch: remove the module"
summary: >
  Mandiant published CVE-2026-131914 on 2026-11-18 for Idunno.AntiCsrf, an open-source anti-CSRF HTTP module for ASP.NET WebForms last released in December 2008: any anonymously reachable page that does not opt out passes a crafted CSRF form field to an unvalidated deserializer, so one POST runs code in the IIS worker process (CVSS 4.0 9.3). Mandiant states that exploitation in the wild has been observed, names no actor, and says the project has no active maintainer or official patch, so the fix is to remove the module, and Mandiant adds that environments with evidence of exploitation should rotate the secrets held in the web configuration and inspect the web root.
discovered_at: "2026-11-19T05:16:00Z"
updated_at: null
event_date: "2026-11-18"
run_id: 2026-11-19T0355Z-intel
priority: notable
immediate_action: null
tags: [vulnerabilities, rce, pre-auth, actively-exploited, no-patch]
regions: [global]
sectors: [technology]
entities: ["product:idunno-anticsrf"]
techniques: [T1190]
affected_products: ["Idunno.AntiCsrf"]
cves:
  - id: CVE-2026-131914
    cvss: "9.3 (CVSS 4.0)"
    epss: null
    type: deserialization
    vector: zero-click
    auth: pre-auth
    status: [exploited, no-patch]
    affected: "Idunno.AntiCsrf.dll 0.9.1.0 (0.9.1 Beta) and earlier, including internally recompiled copies"
    fixed: "none; the project is defunct and Mandiant says to remove the module"
sources:
  - url: "https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md"
    publisher: "Mandiant Vulnerability Disclosures (MNDT-2026-0048, CNA)"
    date: "2026-11-18"
    role: primary
  - url: "https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-129432"
    publisher: "ENISA EUVD (record of CVE-2026-131914)"
    date: "2026-11-19"
    role: corroborating
closed_sources: []
evidence:
  - quote: "Active exploitation in the wild has been observed."
    publisher: "Mandiant Vulnerability Disclosures (MNDT-2026-0048, CNA)"
    source_url: "https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md"
  - quote: "has no active maintainer or official patch available."
    publisher: "Mandiant Vulnerability Disclosures (MNDT-2026-0048, CNA)"
    source_url: "https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md"
verification: single-source
sourcing_note: >
  Mandiant is the CNA, the discoverer and the only source of the exploitation statement, which names no actor, victim count or technique detail and rests on an incident-response case; the ENISA record carries the score and description but not that statement, and dates the record 2026-11-19 where Mandiant's advisory timeline dates its publication 2026-11-18. The project's archived CodePlex page could not be read (it asks for a login), so "no patch" rests on Mandiant's statement that the project has no maintainer or official patch.
confidence: medium
references: []
deep_dive: false
deep_dive_category: null
org_triage: null
classification:
  reliability: B
  credibility: 2
watchlist_hit: false
actions:
  - "Search every ASP.NET WebForms application's Web.config and bin directory for Idunno.AntiCsrf by name, not by file hash because recompiled copies keep the flaw, and remove the module and its DLL, replacing it with a supported anti-forgery mechanism; on any server with evidence of exploitation, such as IIS requests to .aspx pages that returned 302 or 500 with unusually large request sizes, rotate the machineKey, encryption keys and database credentials in Web.config and applicationHost.config, because Mandiant observed exploitation and no patch exists."
updates: []
migrated_from: null
---

Mandiant published advisory MNDT-2026-0048 and CVE-2026-131914 on 2026-11-18 for Idunno.AntiCsrf, a defunct open-source anti-CSRF HTTP module for ASP.NET WebForms, last released as 0.9.1 Beta in December 2008 on the since-retired CodePlex platform and with no active maintainer or official patch ([Mandiant, 2026-11-18](https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)). In the module's PreRequestHandlerExecute step, once the CSRF cookie and the CSRF form field are both non-empty, it deserializes the form field with a parameterless ObjectStateFormatter, which performs no MAC, signature, encryption or machineKey validation and enforces no SerializationBinder restrictions, so a crafted serialized .NET object in that field runs code in the IIS worker process, w3wp.exe; one POST with no prior authentication or valid CSRF token suffices ([Mandiant, 2026-11-18](https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)).

The module runs before the page lifecycle, so any anonymously reachable .aspx page, or any page that relies on application-level session checks inside Page_Load, is reachable unless it opts out through ISuppressCsrfCheck or the SuppressCsrfCheck attribute; pipeline-level authentication rules run earlier and keep anonymous requests away from pages they protect ([Mandiant, 2026-11-18](https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)). After the sink the module raises its own error, so the response is HTTP 302 when customErrors is active and HTTP 500 when its mode is Off, and recompiled or customised copies keep the sink under different file hashes ([Mandiant, 2026-11-18](https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)). Mandiant states that active exploitation in the wild has been observed, names no actor, and says Google's FLARE team completed the root-cause analysis during an incident-response investigation on 2026-11-04 ([Mandiant, 2026-11-18](https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)); the ENISA record scores the flaw CVSS 4.0 9.3 ([ENISA EUVD, 2026-11-19](https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-129432)).

**Exposure:** an ASP.NET WebForms application whose Web.config registers Idunno.AntiCsrf.AntiCsrfModule under httpModules or modules, or whose bin directory holds Idunno.AntiCsrf.dll; Mandiant says to search by name, not by hash ([Mandiant, 2026-11-18](https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)).

**Detection:** IIS logs for anomalous POST requests to .aspx endpoints that return 302 or 500 with elevated request size (cs-bytes, where logged), carrying the module's default cookie __CSRFCOOKIE and form field __CSRFTOKEN, and process-creation telemetry for children of w3wp.exe, which follows from code execution in the worker; if the csrfSettings section is omitted from Web.config, a setter bug overwrites the fallback form field name with RaiseException, so the default field name is not a reliable hunting key on every deployment ([Mandiant, 2026-11-18](https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)).

**Triage:** the module's own tokens are a GUID cookie and a short serialized GUID in the form field, so a cookie that is not a GUID, or a large Base64 value in the CSRF form field, is not legitimate token traffic ([Mandiant, 2026-11-18](https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)).

**Defender takeaway:** remove the module and its DLL and replace it with a supported anti-forgery mechanism, since no patch exists; on environments with evidence of exploitation, Mandiant says to rotate all secrets stored in Web.config and applicationHost.config, machineKey and encryption keys and database credentials included, and to inspect the web roots for unauthorized files ([Mandiant, 2026-11-18](https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)).
