
ACTIVE EXPLOITATION · NO PATCH AVAILABLE[1]
The decision: remove and replace Idunno.AntiCsrf[1]
Mandiant reports that attackers are actively exploiting CVE-2026-131914, an insecure deserialization flaw that can execute code in the IIS worker-process context.[1]
Reporting cutoff: November 22, 2026, 12:34 PM EST (2026-11-22T17:34:00Z).
Practical guidance: Do not wait for a fixed release.[1] The project is defunct, has no active maintainer, and has no official patch; Mandiant’s resolution is to discontinue the library and replace it with a supported anti-CSRF alternative.[1]
0.9.1.0 and 0.9.1 Beta, with the CVE description covering versions through 0.9.1 Beta.[1][2]Who is exposed
Remote, unauthenticated exploitation is possible when the affected module processes a POST request to an anonymously reachable ASP.NET WebForms .aspx page, or to a page that relies only on session checks in Page_Load, unless the page implements ISuppressCsrfCheck or has [SuppressCsrfCheck].[1]
Pipeline-level IIS or ASP.NET authentication and authorization run earlier, so this advisory does not establish that every authenticated page is anonymously exploitable.[1]
What to do now
- Inventory the component. Audit ASP.NET
Web.configfiles and deployedbin/directories forIdunno.AntiCsrforAntiCsrfModule.[1] - Contain reachable exposure while removal is prepared. As practical guidance derived from the documented exposure path, restrict untrusted network access to affected applications and applicable POST routes at a reliable upstream control; test the restriction because it can disrupt legitimate workflows.[1]
- Remove the library completely. Remove its registrations from
<httpModules>and<modules>, remove thecsrfSettingssection and element, remove suppression-code dependencies, and deleteIdunno.AntiCsrf.dllfrom deployedbin/directories.[1] - Replace the protection. Implement and test a supported framework anti-forgery mechanism appropriate to the application; Mandiant does not describe a drop-in fixed release.[1]
- Investigate before declaring recovery complete. Review IIS logs for anomalous POSTs to
.aspxendpoints that return HTTP 302 or 500 with elevatedcs-bytes, where that field is logged.[1] Treat those patterns as triage leads, not unique proof of exploitation.[1] - If evidence of exploitation exists, respond as an incident. Mandiant advises rotating secrets stored in
Web.configandapplicationHost.configand inspecting webroots for unauthorized files.[1]
Evidence boundary: Bounded evidence check: Through the reporting cutoff, exact case-insensitive searches of the captured Mandiant advisory and CVE record found zero matches for the recorded query sets covering unique network IOCs, actor attribution, campaign names, and victim counts.[1][2] Mandiant reports observed exploitation in the wild.[1] The CVE was not present in the captured CISA KEV catalog version 2026.11.20, released 2026-11-20T17:48:39.1516Z; that bounded catalog absence does not negate Mandiant’s affirmative report.[3][1]
Sources
- Mandiant MNDT-2026-0048 — captured before the reporting cutoff.
- CVE Program record for CVE-2026-131914 — published 2026-11-19T01:29:12.970Z.
- CISA Known Exploited Vulnerabilities Catalog — captured catalog version 2026.11.20, released 2026-11-20T17:48:39.1516Z.
