Advisory record · GHSA-5p3x-r448-pc62

Improper Verification of Cryptographic Signature in PySAML2

CVSS 6.5 MediumEPSS 0.013 · 70th percentile

Published by the GitHub Advisory Database at 21 Jan 2021, 14:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pysaml2PyPI<6.5.06.5.0
Identifiers
GHSA-5p3x-r448-pc62 · CVE-2021-21239 · PYSEC-2021-49
Weakness (CWE)
CWE-347
Published
21 Jan 2021
Updated
10 Sept 2026

Machine-written summary

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

pysaml2 versions before 6.5.0 are affected. When using the default CryptoBackendXmlSec1 backend, the xmlsec1 tool accepts any key type found in a signed SAML document during verification, so the signature may not be checked against a trusted certificate. An attacker who can supply a SAML document to the application may be able to forge a signed document that is accepted. Upgrade to pysaml2 6.5.0. No workaround is listed.

Written 5 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
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.013, the 70th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:37 UTC First seen by agentprime
  2. 31 Oct 2026, 14:37 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.