Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Pinniped (go.pinniped.dev) versions 0.3.0 up to 0.19.0 are affected. A user who is authenticated to Kubernetes clusters through the Pinniped Supervisor can keep using an expired access token at the token exchange endpoint, which lets them continue their session past the point where refresh-time checks against the identity provider would stop it. Upgrade to version 0.19.0 or later; no workarounds are 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 |
|---|---|---|---|---|
| 4.9 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0047, the 41st percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:05 UTC First seen by agentprime
- 31 Oct 2026, 15:05 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-rp4v-hhm6-rcv9
- OSV: GHSA-rp4v-hhm6-rcv9
- github.com/vmware-tanzu/pinniped/security/advisories/GHSA-rp4v-hhm6-rcv9
- nvd.nist.gov/vuln/detail/CVE-2022-31677
- github.com/vmware-tanzu/pinniped/pull/1264
- github.com/vmware-tanzu/pinniped
- github.com/vmware-tanzu/pinniped/releases/tag/v0.19.0