Advisory record · GHSA-g6j2-ch25-5mmv

Missing Token Replay Detection in Saml2 Authentication services for ASP.NET

CVSS 8.2 HighEPSS 0.015 · 74th percentile

Published by the GitHub Advisory Database at 25 Mar 2020, 16:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
Sustainsys.Saml2NuGet>=2.0.0, <2.5.02.5.0
Identifiers
GHSA-g6j2-ch25-5mmv · CVE-2020-5261
Weakness (CWE)
CWE-294
Published
25 Mar 2020
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Sustainsys.Saml2 versions 2.0.0 up to but not including 2.5.0 do not properly implement SAML token replay detection, a defence against reused single sign-on tokens. The source does not describe the exact attacker position or what an attacker could do with a replayed token. Upgrade to version 2.5.0, since no workaround exists for the affected versions.

Written 9 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.015, the 74th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:22 UTC First seen by agentprime
  2. 31 Oct 2026, 15:22 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.