{"answers":{"affected":"3 open source packages ship an affected version, including scitokens. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32727 exists.","fix":"Upgrade scitokens to 1.9.7 or later.","what":"CVE-2026-32727 is a high-severity path traversal vulnerability in scitokens, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32727 and fix it if it is affected.\n\nWhat it is: CVE-2026-32727 is a high-severity path traversal vulnerability in scitokens, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32727 exists.\n\nAffected packages and fixed versions:\n- scitokens (PyPI): affected all versions; fixed in 1.9.7\n- scitokens (PyPI): affected all versions; fixed in 1.9.7\n- scitokens (PyPI): affected all versions; fixed in 1.9.7\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32727/ (Markdown: https://insights.sbomify.com/CVE-2026-32727/index.md)","id":"CVE-2026-32727","markdown":"https://insights.sbomify.com/CVE-2026-32727/index.md","name":"CVE-2026-32727","record":{"aliases":["GHSA-3x2w-63fp-3qvw","PYSEC-2026-2277"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SciTokens library","requires_auth":"low_privilege","summary":"Attackers can bypass directory restrictions in SciTokens by using path traversal sequences in token scopes, allowing unauthorized access to protected resources.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"scitokens_library","vendor":"scitokens"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"SciTokens: Authorization Bypass via Path Traversal in Scope Validation","id":"CVE-2026-32727","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Parse Server has a stored XSS filter bypass via Content-Type MIME parameter and missing XML extension blocklist entries","id":"CVE-2026-32728"},"packages":[{"ecosystem":"PyPI","fixed":["1.9.7"],"introduced":["0"],"last_affected":[],"package":"scitokens","purl":null,"source":"GHSA-3x2w-63fp-3qvw"},{"ecosystem":"PyPI","fixed":["1.9.7"],"introduced":["0"],"last_affected":[],"package":"scitokens","purl":"pkg:pypi/scitokens","source":"GHSA-3x2w-63fp-3qvw"},{"ecosystem":"PyPI","fixed":["1.9.7"],"introduced":["0"],"last_affected":[],"package":"scitokens","purl":"pkg:pypi/scitokens","source":"PYSEC-2026-2277"}],"prev":{"headline":"SciTokens C++: Sibling-Path Authorization Bypass","id":"CVE-2026-32726"},"products":["scitokens"],"published":"2026-03-31","related":[{"cvss_score":9.8,"headline":"SciTokens vulnerable to SQL Injection in KeyCache","id":"CVE-2026-32714","kev_date_added":null,"published":"2026-03-31"},{"cvss_score":8.1,"headline":"SciTokens: Authorization Bypass via Incorrect Scope Path Prefix Checking","id":"CVE-2026-32716","kev_date_added":null,"published":"2026-03-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["scitokens"]},"summary":"Attackers can bypass directory restrictions in SciTokens by using path traversal sequences in token scopes, allowing unauthorized access to protected resources.","url":"https://insights.sbomify.com/CVE-2026-32727/"}