Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
SciTokens versions before 1.9.6 incorrectly check scope paths using a simple prefix match, so a token authorized for a path such as /john can also access sibling paths sharing that prefix, such as /johnathan. An attacker holding a valid token for one path can read or write resources belonging to another user with a matching name prefix, which is an authorization bypass. Upgrade to SciTokens 1.9.6, which fixes the issue.
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 |
|---|---|---|---|---|
| 8.1 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0040, the 35th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:04 UTC First seen by agentprime
- 31 Oct 2026, 15:04 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-w8fp-g9rh-34jh
- OSV: GHSA-w8fp-g9rh-34jh
- github.com/scitokens/scitokens/security/advisories/GHSA-w8fp-g9rh-34jh
- nvd.nist.gov/vuln/detail/CVE-2026-32716
- github.com/scitokens/scitokens/commit/7a237c0f642efb9e8c36ac564b745895cca83583
- github.com/scitokens/scitokens
- github.com/scitokens/scitokens/releases/tag/v1.9.6