Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Wizkunde SAMLBase (gogentooss/samlbase) versions before 1.2.7 may incorrectly use the results of XML DOM traversal and canonicalization, so an attacker may be able to alter SAML data without invalidating the signature. This could allow bypassing authentication to SAML service providers. Upgrade to version 1.2.7 or later. The source gives few details about the required attacker position.
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 |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.017, the 77th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:31 UTC First seen by agentprime
- 31 Oct 2026, 14:31 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-7gh2-8q93-87hp
- OSV: GHSA-7gh2-8q93-87hp
- nvd.nist.gov/vuln/detail/CVE-2018-5387
- github.com/GoGentoOSS/SAMLBase/issues/3
- github.com/GoGentoOSS/SAMLBase/commit/482cdf8c090e0f1179073034ebcb609ac7c3f5b3
- duo.com/blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations
- github.com/GoGentoOSS/SAMLBase
- www.kb.cert.org/vuls/id/475445