Authenticated sibling-path access via prefix comparison
Published Mar 31, 2026 · Updated Mar 31, 2026
Authorization bypass in SciTokens C++ before 1.4.1 allows remote authenticated users to access sibling paths sharing an authorized prefix. Enforcer::scope_validator compares the requested resource path with the token scope using a raw string-prefix test that omits a path-segment boundary check. A valid scoped token is required, and exploitation grants read or write access to adjacent namespaces only when their names begin with the authorized path.
Summary
What happened
Authorization bypass in SciTokens C++ before 1.4.1 allows remote authenticated users to access sibling paths sharing an authorized prefix. Enforcer::scope_validator compares the requested resource path with the token scope using a raw string-prefix test that omits a path-segment boundary check. A valid scoped token is required, and exploitation grants read or write access to adjacent namespaces only when their names begin with the authorized path.
The record
- CVE
- CVE-2026-32726
- Published
- Mar 31, 2026
- Updated
- Mar 31, 2026
- Vendor
- SciTokens
- Product
- SciTokens C++
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 31, 2026CVE publishedPublication date reported by the CVE source.
- Mar 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Sibling-prefix authorization proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo