CVE-2020-5268
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 1.09 % · percentile 65.99 % · scored 18 Nov 2026.
Saved 18 Nov 2026 15:46:44 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
In Saml2 Authentication Services for ASP.NET versions before 1.0.2, and between 2.0.0 and 2.6.0, there is a vulnerability in how tokens are validated in some cases. Saml2 tokens are usually used as bearer tokens - a caller that presents a token is assumed to be the subject of the token. There is also support in the Saml2 protocol for issuing tokens that is tied to a subject through other means, e.g. holder-of-key where possession of a private key must be proved. The Sustainsys.Saml2 library incorrectly treats all incoming tokens as bearer tokens, even though they have another subject confirmation method specified. This could be used by an attacker that could get access to Saml2 tokens with another subject confirmation method than bearer. The attacker could then use such a token to create a log in session. This vulnerability is patched in versions 1.0.2 and 2.7.0.
Read the publisher's advisoryIn Saml2 Authentication Services for ASP.NET versions before 1.0.2, and between 2.0.0 and 2.6.0, there is a vulnerability in how tokens are validated in some cases. Saml2 tokens are usually used as bearer tokens - a caller that presents a token is assumed to be the subject of the token. There is also support in the Saml2 protocol for issuing tokens that is tied to a subject through other means, e.g. holder-of-key where possession of a private key must be proved. The Sustainsys.Saml2 library incorrectly treats all incoming tokens as bearer tokens, even though they have another subject confirmation method specified. This could be used by an attacker that could get access to Saml2 tokens with another subject confirmation method than bearer. The attacker could then use such a token to create a log in session. This vulnerability is patched in versions 1.0.2 and 2.7.0.
Read the publisher's advisoryIn Saml2 Authentication Services for ASP.NET versions before 1.0.2, and between 2.0.0 and 2.6.0, there is a vulnerability in how tokens are validated in some cases. Saml2 tokens are usually used as bearer tokens - a caller that presents a token is assumed to be the subject of the token. There is also support in the Saml2 protocol for issuing tokens that is tied to a subject through other means, e.g. holder-of-key where possession of a private key must be proved. The Sustainsys.Saml2 library incorrectly treats all incoming tokens as bearer tokens, even though they have another subject confirmation method specified. This could be used by an attacker that could get access to Saml2 tokens with another subject confirmation method than bearer. The attacker could then use such a token to create a log in session. This vulnerability is patched in versions 1.0.2 and 2.7.0.
Read the publisher's advisory### Impact Saml2 tokens are usually used as bearer tokens - a caller that presents a token is assumed to be the subject of the token. There is also support in the Saml2 protocol for issuing tokens that is tied to a subject through other means, e.g. holder-of-key where possession of a private key must be proved. The Sustainsys.Saml2 library incorrectly treats all incoming tokens as bearer tokens, even though they have another subject confirmation method specified. This could be used by an attacker that could get access to Saml2 tokens with another subject confirmation method than bearer. The attacker could then use such a tocken to create a log in session. ### Patches Version 1.0.2 and 2.7.0 are patched. ### Workarounds Ensure that any IdentityProvider trusted by the Sustainsys.Saml2 SP only issues bearer tokens if the audience matches the Sustainsys.Saml2 SP. ### For more information If you have any questions or comments about this advisory: * Comment on #103 * Email us at [email protected] if you think that there are further security issues.
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 1.09 % · percentile 65.99 % · scored 18 Nov 2026.
Saved 18 Nov 2026 15:46:44 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2020-5268 · 18 Nov 2026 15:46:44 UTC
CVE-2020-5268 · 17 Nov 2026 15:26:11 UTC
CVE-2020-5268 · 17 Nov 2026 02:39:16 UTC
CVE-2020-5268 · 15 Nov 2026 14:45:34 UTC
CVE-2020-5268 · 14 Nov 2026 16:37:01 UTC
CVE-2020-5268 · 13 Nov 2026 19:59:34 UTC
CVE-2020-5268 · 12 Nov 2026 18:18:51 UTC
CVE-2020-5268 · 10 Nov 2026 20:24:10 UTC
CVE-2020-5268 · 09 Nov 2026 21:04:24 UTC
CVE-2020-5268 · 08 Nov 2026 15:12:21 UTC
CVE-2020-5268 · 07 Nov 2026 16:07:52 UTC
CVE-2020-5268 · 06 Nov 2026 19:10:17 UTC
CVE-2020-5268 · 05 Nov 2026 22:49:22 UTC
CVE-2020-5268 · 05 Nov 2026 02:54:06 UTC
CVE-2020-5268 · 03 Nov 2026 16:59:18 UTC
CVE-2020-5268 · 02 Nov 2026 23:59:04 UTC
CVE-2020-5268 · 01 Nov 2026 23:58:58 UTC
CVE-2020-5268 · 01 Nov 2026 03:04:52 UTC
CVE-2020-5268 · 31 Oct 2026 01:52:30 UTC
CVE-2020-5268 · 29 Oct 2026 18:29:26 UTC
CVE-2020-5268 · 28 Oct 2026 19:55:37 UTC
CVE-2020-5268 · 27 Oct 2026 15:46:19 UTC
CVE-2020-5268 · 27 Oct 2026 00:23:05 UTC
CVE-2020-5268 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
euvd · EUVD-2020-0374 · Published
nvd · CVE-2020-5268 · Published
osv · GHSA-9475-xg6m-j7pw · Published
cve-program · CVE-2020-5268 · Published