How severe is CVE-2020-5261?

CVE-2020-5261 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2020-5261 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-5261?

CVE-2020-5261 affects Sustainsys Saml2. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-5261?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-5261 published?

CVE-2020-5261 was published on 2020-03-25 and last updated on 2026-06-17.

CVE-2020-5261

CVE-2020-5261 is a high-severity vulnerability in Sustainsys Saml2 with a CVSS 3.x base score of 8.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-294.

Key facts

Severity: High (CVSS 3.x base score 8.2)
CVSS v2: 4.9
EPSS exploit prediction: 1% (73rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-294
Affected product: Sustainsys Saml2
Published: 2020-03-25
Last modified: 2026-06-17

Description

Saml2 Authentication services for ASP.NET (NuGet package Sustainsys.Saml2) greater than 2.0.0, and less than version 2.5.0 has a faulty implementation of Token Replay Detection. Token Replay Detection is an important defence in depth measure for Single Sign On solutions. The 2.5.0 version is patched. Note that version 1.0.1 is not affected. It has a correct Token Replay Implementation and is safe to use. Saml2 Authentication services for ASP.NET (NuGet package Sustainsys.Saml2) greater than 2.0.0, and less than version 2.5.0 have a faulty implementation of Token Replay Detection. Token Replay Detection is an important defense measure for Single Sign On solutions. The 2.5.0 version is patched. Note that version 1.0.1 and prior versions are not affected. These versions have a correct Token Replay Implementation and are safe to use.

Frequently asked questions

What is CVE-2020-5261?: Saml2 Authentication services for ASP.NET (NuGet package Sustainsys.Saml2) greater than 2.0.0, and less than version 2.5.0 has a faulty implementation of Token Replay Detection. Token Replay Detection is an important defence in depth measure for Single Sign On solutions. The 2.5.0 version is patched. Note that version 1.0.1 is not affected. It has a correct Token Replay Implementation and is safe to use. Saml2 Authentication services for ASP.NET (NuGet package Sustainsys.Saml2) greater than 2.0.0, and less than version 2.5.0 have a faulty implementation of Token Replay Detection. Token Replay Detection is an important defense measure for Single Sign On solutions. The 2.5.0 version is patched. Note that version 1.0.1 and prior versions are not affected. These versions have a correct Token Replay Implementation and are safe to use.
How severe is CVE-2020-5261?: CVE-2020-5261 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2020-5261 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-5261?: CVE-2020-5261 affects Sustainsys Saml2. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-5261?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-5261 published?: CVE-2020-5261 was published on 2020-03-25 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:sustainsys:saml2:*:*:*:*:*:*:*:*

More vulnerabilities in Sustainsys Saml2

CVE-2023-41890 — High (CVSS 7.5): Sustainsys.Saml2 library adds SAML2P support to ASP.NET web sites, allowing the web site to act as a SAML2 Service…
CVE-2020-5268 — Medium (CVSS 6.5): In Saml2 Authentication Services for ASP.NET versions before 1.0.2, and between 2.0.0 and 2.6.0, there is a…

All CVEs affecting Sustainsys Saml2 →

Other CWE-294 (Authentication Bypass by Capture-replay) vulnerabilities

CVE-2025-49752 — Critical (CVSS 10.0): Azure Bastion Elevation of Privilege Vulnerability
CVE-2026-88278 — Critical (CVSS 9.8): GeoVision GV-LPC2211 V1.13 fails to enforce WS-Security UsernameToken freshness or nonce reuse protection, allowing a…
CVE-2026-86219 — Critical (CVSS 9.8): Authen::SASL::Perl::DIGEST_MD5 versions before 2.2100 for Perl accept replayed authentication responses via unverified…
CVE-2026-65905 — Critical (CVSS 9.8): Authentication Bypass by Capture-replay vulnerability in Apache Tomcat's DIGEST authenticator. If, before windowSize…
CVE-2026-68079 — Critical (CVSS 9.8): In Apache CXF's DefaultEncryptingCodeDataProvider, a captured authorization code can be redeemed an unlimited number…
CVE-2026-28564 — Critical (CVSS 9.8): Insufficient Session Expiration, Authentication Bypass by Capture-replay vulnerability in Apache IoTDB. REST Basic…

Browse all CWE-294 (Authentication Bypass by Capture-replay) vulnerabilities →