Skip to main content
Menu
CVEs

CVE

Idunno AntiCsrf remote code execution in ASP.NET CSRF token validation

Only affects Idunno.AntiCsrf 0.9.1 Beta (0.9.1.0) used in ASP.NET WebForms applications. CVSS rates it critical at 9.3. No fixed version is listed in the checked facts.

CVE-2026-131914EUVD-2026-129432Published Updated Summary written by a model

9.3CriticalCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Do first: Workaround: The checked facts list no fix and no workaround. The advisory's conditions point to ASP.NET Page endpoints that do not implement ISuppressCsrfCheck or use the SuppressCsrfCheck attribute.

Summary

The Idunno AntiCsrf software for ASP.NET unsafely deserializes untrusted data during its double-submit cookie and form field validation. A remote attacker can exploit this through object injection to execute code, without logging in over the network.

Original description

Deserialization of untrusted data in double-submit cookie vs. form field validation in Idunno.AntiCsrf versions through 0.9.1 Beta on ASP.NET allows remote unauthenticated attackers to execute code via object injection

Who should check

Teams running Idunno.AntiCsrf 0.9.1 Beta on ASP.NET WebForms sites, such as IIS-hosted web applications

“version 0.9.1.0 / 0.9.1 Beta”

github.com

cve.now Index

35Pcve.now Index 35 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 40 if advisories confirm default setups are exposed

What to do

  • Workaround: The checked facts list no fix and no workaround. The advisory's conditions point to ASP.NET Page endpoints that do not implement ISuppressCsrfCheck or use the SuppressCsrfCheck attribute.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131914 (Deserialization of untrusted data in CodePlex AntiCSRF), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131914 (entry last updated 2026-11-19):
Affected:
- Idunno AntiCsrf: through 0.9.1.0; through 0.9.1 Beta
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Idunno.AntiCsrf version 0.9.1 Beta (0.9.1.0) used in an ASP.NET WebForms application (source: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)
- A POST to an ASP.NET Page endpoint that does not implement ISuppressCsrfCheck or use the SuppressCsrfCheck attribute (source: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-131914 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131914 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md
- https://codeplexarchive.org/project/AntiCSRF
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131914
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131914"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Record last updated
  5. Posted on X by cve.now

Affected versions

  • Idunno AntiCsrf

    through 0.9.1.0; through 0.9.1 Beta

Evidence 4

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-131914

Is CVE-2026-131914 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The AntiCsrf library deserializes untrusted data, which can allow arbitrary code execution in the IIS worker process (w3wp.exe). The advisory says this can lead to complete compromise of the web application server.Source: github.com

Which versions are affected by CVE-2026-131914?

AntiCsrf: through 0.9.1.0; through 0.9.1 Beta.Source: cve.now feed data

Am I affected, and how do I check?

Idunno.AntiCsrf versions 0.9.1.0 and 0.9.1 Beta, used in an ASP.NET WebForms application. The relevant setup is a POST to an ASP.NET Page endpoint that neither implements ISuppressCsrfCheck nor uses the SuppressCsrfCheck attribute. To check, look at the Idunno.AntiCsrf version referenced by the project.Source: github.com

How do I fix CVE-2026-131914?

The checked facts name no fixed version and no vendor patch IDs, so no upgrade target can be given from them. Check the vendor's advisory for an updated release.Source: github.com

What if there's no patch?

The checked facts list no fix and no workaround. The advisory's conditions point to ASP.NET Page endpoints that do not implement ISuppressCsrfCheck or use the SuppressCsrfCheck attribute.Source: github.com

More CVEs