Read the docs
TI-2025-18597 Aliases CVE-2025-24895GHSA-vq63-8f72-f486

SAML Response Signature Verification Bypass in CIE.AspNetCore.Authentication

Priority HIGH 78CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-287.

Summary

CIE.AspNetCore.Authentication is an AspNetCore Remote Authenticator for CIE 3.0. Authentication using Spid and CIE is based on the SAML2 standard which provides two entities: 1. Identity Provider (IDP): the system that authenticates users and provides identity information (SAML affirmation) to the Service Provider, in essence, is responsible for the management of the credentials and identity of users; 2. Service Provider (SP): the system that provides a service to the user and relies on the Identity Provider to authenticate the user, receives SAML assertions from the IdP to grant access to resources. The library cie-aspnetcore refers to the second entity, the SP, and implements the validation logic of SAML assertions within SAML responses. In affected versions there is no guarantee that the first signature refers to the root object, it follows that if an attacker injects an item signed as the first element, all other signatures will not be verified. The only requirement is to have an XML element legitimately signed by the IdP, a condition that is easily met using the IdP's public metadata. An attacker could create an arbitrary SAML response that would be accepted by SPs using vulnerable SDKs, allowing him to impersonate any Spid and/or CIE user. This issue has been addressed in version 2.1.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00607 49th percentileScored 2026-11-07
Fix Fixed cie-aspnetcore (italia): 2.1.0CIE.AspNetCore.Authentication (NuGet): 2.1.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
italiacie-aspnetcorebefore 2.1.02.1.0Patch availableCNA
—CIE.AspNetCore.Authentication (NuGet)before 2.1.02.1.0Patch availableGHSA-vq63-8f72-f486
  • cie-aspnetcore Vendoritalia Affected before 2.1.0 Fixed in 2.1.0 Patch available CNA
  • CIE.AspNetCore.Authentication (NuGet) Vendor— Affected before 2.1.0 Fixed in 2.1.0 Patch available GHSA-vq63-8f72-f486

Remediation

  • Fix · CNA cie-aspnetcore (italia) Fixed in 2.1.0
  • Fix · GHSA-vq63-8f72-f486 CIE.AspNetCore.Authentication (NuGet) Fixed in 2.1.0 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2025-24895
  2. 2026-10-03 Alias added: GHSA-vq63-8f72-f486

References

  • TI-2025-18596 SAML Response Signature Verification Bypass in SPID.AspNetCore.Authentication CVSS 3.1CRITICAL 9.1
  • TI-2025-01550 Design Comuni Italia < 1.1.2 - Unauthenticated Stored XSS CVSS 3.1MEDIUM 6.1

Sources