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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 14:37 UTC First seen by agentprime
- 31 Oct 2026, 14:37 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-5p3x-r448-pc62
- OSV: GHSA-5p3x-r448-pc62
- github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62
- nvd.nist.gov/vuln/detail/CVE-2021-21239
- github.com/IdentityPython/pysaml2/commit/46578df0695269a16f1c94171f1429873f90ed99
- github.com/IdentityPython/pysaml2
- github.com/IdentityPython/pysaml2/releases/tag/v6.5.0
- github.com/pypa/advisory-database/tree/main/vulns/pysaml2/PYSEC-2021-49.yaml
- lists.debian.org/debian-lts-announce/2021/02/msg00038.html
- pypi.org/project/pysaml2
- www.aleksey.com/pipermail/xmlsec/2013/009717.html