Path Traversal in scitokens (CVE-2026-32727)
Summary
Path traversal in scitokens (CVE-2026-32727). Confidential information can be exposed externally. Exploitable via Enforcer. Mitigation: upgrade to 1.9.7 or later.
Original description
The description as published by the source.
SciTokens is a reference library for generating and using SciTokens. Prior to version 1.9.7, the Enforcer is vulnerable to a path traversal attack where an attacker can use dot-dot (..) in the scope claim of a token to escape the intended directory restriction. This occurs because the library normalizes both the authorized path (from the token) and the requested path (from the application) before comparing them using startswith. This issue has been patched in version 1.9.7.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32727 has been found in scitokens.
Attackers can target a specific entry point like Enforcer over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade scitokens to 1.9.7 or later.
If unsure, ask your IT team or search "scitokens CVE-2026-32727" on the vendor's site.
CVE-2026-32727 (scitokens) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Enforcer / scope / startswith / _check_scope
Patched: 1.9.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in scitokens. Attackers reach the vulnerable code path via Enforcer.
Check the vendor advisory for the affected versions of scitokens. Attack surface: Enforcer / scope / startswith / _check_scope.
Severity: ?. Confidential information can be exposed externally.
Update to 1.9.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'scitokens' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'scitokens' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
scitokensを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade scitokens to 1.9.7ステージング環境で 1.9.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com