CVE-2026-131914: Idunno.AntiCsrf Is Actively Exploited—Remove and Replace It

Mandiant reports active exploitation of a critical Idunno.AntiCsrf deserialization flaw. The project is defunct and has no patch, so affected organizations should remove and replace the library. As practical guidance derived from the documented exposure path, contain reachable exposure and investigate for compromise.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

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]

Affected releases The captured primary records identify 0.9.1.0 and 0.9.1 Beta, with the CVE description covering versions through 0.9.1 Beta.[1][2]
Severity CVSS v4.0 score 9.3 Critical (CVSS-BT).[1]
Weakness CWE-502: Deserialization of Untrusted Data.[1]

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

  1. Inventory the component. Audit ASP.NET Web.config files and deployed bin/ directories for Idunno.AntiCsrf or AntiCsrfModule.[1]
  2. 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]
  3. Remove the library completely. Remove its registrations from <httpModules> and <modules>, remove the csrfSettings section and element, remove suppression-code dependencies, and delete Idunno.AntiCsrf.dll from deployed bin/ directories.[1]
  4. 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]
  5. Investigate before declaring recovery complete. Review IIS logs for anomalous POSTs to .aspx endpoints that return HTTP 302 or 500 with elevated cs-bytes, where that field is logged.[1] Treat those patterns as triage leads, not unique proof of exploitation.[1]
  6. If evidence of exploitation exists, respond as an incident. Mandiant advises rotating secrets stored in Web.config and applicationHost.config and 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

  1. Mandiant MNDT-2026-0048 — captured before the reporting cutoff.
  2. CVE Program record for CVE-2026-131914 — published 2026-11-19T01:29:12.970Z.
  3. CISA Known Exploited Vulnerabilities Catalog — captured catalog version 2026.11.20, released 2026-11-20T17:48:39.1516Z.