Is github.com/crewjam/saml 0.5 vulnerable?
Go · 3 releases from 0.5.0 to 0.5.2 · latest github.com/crewjam/saml is 0.6.3 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. github.com/crewjam/saml 0.5.2, the last 0.5 release, is affected by 1 known security advisory (1 low). At least one has no fixed release yet.
Is your project on an affected github.com/crewjam/saml?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/crewjam/saml 0.5.2
Nil-pointer panic in validateAssertion and namespace-blind Subject.NameID in github.com/crewjam/saml
- Affected
- All versions
- Fixed in
- No fix released
Every github.com/crewjam/saml 0.5.x release
Affected: 0.5.0 to 0.5.2. Latest github.com/crewjam/saml: 0.6.3.
| Version | Known advisories |
|---|---|
| github.com/crewjam/saml 0.5.2 | GO-2026-6909 |
| github.com/crewjam/saml 0.5.1 | GO-2026-6909 |
| github.com/crewjam/saml 0.5.0 | GO-2026-6909 |
Which of your client projects are still on github.com/crewjam/saml 0.5?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/crewjam/saml version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/crewjam/saml versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.