What is CVE-2025-24894?

CVE-2025-24894 is a critical-severity security vulnerability in SPID.AspNetCore.Authentication (nuget), affecting versions <= 3.3.0. It is fixed in 3.4.0.

How severe is CVE-2025-24894?

CVE-2025-24894 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of SPID.AspNetCore.Authentication are affected by CVE-2025-24894?

SPID.AspNetCore.Authentication (nuget) versions <= 3.3.0 is affected.

Is there a fix for CVE-2025-24894?

Yes. CVE-2025-24894 is fixed in 3.4.0. Upgrade to this version or later.

Is CVE-2025-24894 exploitable, and should I be worried?

Whether CVE-2025-24894 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-24894 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-24894 in SPID.AspNetCore.Authentication

Q: How severe is CVE-2025-24894?

CVE-2025-24894 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of SPID.AspNetCore.Authentication are affected by CVE-2025-24894?

SPID.AspNetCore.Authentication (nuget) versions <= 3.3.0 is affected.

Q: Is there a fix for CVE-2025-24894?

Yes. CVE-2025-24894 is fixed in 3.4.0. Upgrade to this version or later.

Q: Is CVE-2025-24894 exploitable, and should I be worried?

Whether CVE-2025-24894 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-24894 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-24894?

Upgrade SPID.AspNetCore.Authentication to 3.4.0 or later.

Summary

The AspNetCore Remote Authenticator for SPID Allows SAML Response Signature Verification Bypass

Impact

An attacker could craft an arbitrary SAML response that would be accepted by SPs using the vulnerable SDKs, allowing him to impersonate any Spid and/or CIE user.

CVE-2025-24894 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.4.0); upgrading removes the vulnerable code path.

Affected versions

SPID.AspNetCore.Authentication (<= 3.3.0)

Security releases

SPID.AspNetCore.Authentication → 3.4.0 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade SPID.AspNetCore.Authentication to 3.4.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-24894? CVE-2025-24894 is a critical-severity security vulnerability in SPID.AspNetCore.Authentication (nuget), affecting versions <= 3.3.0. It is fixed in 3.4.0.
How severe is CVE-2025-24894? CVE-2025-24894 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of SPID.AspNetCore.Authentication are affected by CVE-2025-24894? SPID.AspNetCore.Authentication (nuget) versions <= 3.3.0 is affected.
Is there a fix for CVE-2025-24894? Yes. CVE-2025-24894 is fixed in 3.4.0. Upgrade to this version or later.
Is CVE-2025-24894 exploitable, and should I be worried? Whether CVE-2025-24894 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-24894 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-24894? Upgrade SPID.AspNetCore.Authentication to 3.4.0 or later.