Loading vulnerability…
CVE-2026-32727 is a path traversal vulnerability in the SciTokens reference library affecting versions prior to 1.9.7. The flaw is in the Enforcer component’s authorization logic for token scope paths. An attacker can include dot-dot (..) path segments in a token’s scope claim to escape the intended directory restriction. The issue arises because the library normalizes both the authorized path derived from the token and the requested path supplied by the application, then compares them using a startswith check. This normalization-and-prefix-validation approach can incorrectly treat attacker-controlled paths as authorized, allowing traversal outside the intended directory boundary.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.