← Back to results
Vulnerability record · public intelligence
CVE-2026-32726
HIGH

SciTokens C++: Sibling-Path Authorization Bypass

Published Mar 31, 2026 · Updated Oct 23, 2026

Severity · CVSSHIGH · 8.1
Known exploitationNot listed
EPSS / likelihood0.38%
QFinch risk score10 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

SciTokens C++: Sibling-Path Authorization Bypass

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

SciTokens C++ is a minimal library for creating and using SciTokens from C or C++. Prior to version 1.4.1, scitokens-cpp is vulnerable to an authorization bypass in path-based scope validation. The enforcer used a simple string-prefix comparison when checking whether a requested resource path was covered by a token's authorized scope path. Because the check did not require a path-segment boundary, a token scoped to one path could incorrectly authorize access to sibling paths that merely started with the same prefix. This issue has been patched in version 1.4.1.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
MEDIUM
Confidence
10%
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗

Record history

Published Mar 31, 2026 · Last refreshed Oct 23, 2026