CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to the live brief
NOTABLECVE-2026-131914exploitedNATOB2vulnerability

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)

Idunno.AntiCsrf (ASP.NET WebForms) unauthenticated deserialization RCE exploited, no patch: remove the module

Defender 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.

Analysis

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). 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).

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). 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). 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); the ENISA record scores the flaw CVSS 4.0 9.3 (ENISA EUVD, 2026-11-19).

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).

Cited evidence

Active exploitation in the wild has been observed.

has no active maintainer or official patch available.

Mandiant Vulnerability Disclosures (MNDT-2026-0048, CNA) 2026-11-18

Sources2

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.