External risk intelligence

Idunno AntiCsrf Remote Code Execution via Deserialization

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-131914

The vulnerability affects a library specifically designed for anti-CSRF protection in web applications. Because CSRF protection mechanisms are implemented directly within public-facing web applications to secure user sessions and form submissions, the vulnerable surface is commonly exposed to the internet as part of the application's standard web request handling process.

Deserialization

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A deserialization vulnerability in the Idunno.AntiCsrf library allows unauthenticated remote attackers to potentially execute code by injecting malicious objects. This matters because the library is designed to protect against Cross-Site Request Forgery attacks, and a flaw here could undermine that security. The primary concern is confirming whether this specific library is in use and, if so, understanding the exposure.

  • Untrusted data can cause code execution.
  • Protects against CSRF but has its own flaw.
  • Confirm use and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending a specially crafted request to a web application using the vulnerable component. This request would leverage the component's method of validating cookies against form fields to inject a malicious object. Successful exploitation could lead to remote code execution, allowing the attacker to compromise the application.

  • No authentication required.
  • Triggered by crafted request.
  • Leads to remote code execution.

Live Threat

Current exploitation, exposure, and threat context

Remote, unauthenticated attackers could execute arbitrary code on systems running vulnerable versions of the AntiCSRF library when processing untrusted data through specific validation paths. This could affect the integrity and availability of the affected service.

  • System code execution.
  • Untrusted data deserialization.
  • Service compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in an anti-CSRF library likely impacts application owners and platform teams responsible for web application security. The initial step is to identify all instances of the affected library, determine their exposure and business criticality, and then engage the appropriate application or platform owner to plan remediation.

  • Own the issue via application or platform teams.
  • Verify reachability and business criticality.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Idunno.AntiCsrf?

Idunno.AntiCsrf is a library for ASP.NET applications built to stop Cross-Site Request Forgery (CSRF) attacks. These attacks trick web browsers into performing unwanted actions on a site where the user is logged in. Developers integrate this component into their web applications to validate that requests are legitimate, typically by comparing data between cookies and form fields.

What does CWE-502 mean for CVE-2026-131914?

CWE-502 refers to the deserialization of untrusted data. When an application takes data from an outside source and converts it back into an object without proper checks, it can be dangerous. In the context of this CVE, the library fails to safely handle this process, allowing an attacker to inject a specially crafted object that the application then executes as code.

How is this vulnerability triggered?

An attacker triggers this by sending a malformed request to a web application using the affected library. The bug exists in the validation path where cookies are checked against form fields. Simply visiting a site or interacting normally does not trigger it; the request must contain a specifically prepared malicious object designed to exploit the flawed deserialization process.

Is my application at risk?

Halo Surface Signal indicates that because this library is designed to secure public-facing web request handling, it is likely exposed to the internet. If your application uses Idunno.AntiCsrf versions 0.9.1 Beta or earlier to process incoming traffic, it is effectively within the reach of remote attackers, regardless of whether the system is on an internal network or public-facing.

How do I respond to this vulnerability?

The priority is to locate all applications in your environment that include the Idunno.AntiCsrf library. Once you identify which services rely on this component, assess their business importance and reachability. Coordinate with your application and platform engineering teams to plan a remediation strategy, as this library is likely integrated deep into your application's request processing logic.

References