Loading story…
Two SciTokens projects disclosed high-severity path traversal flaws that could let attackers bypass directory-based authorization controls by manipulating token scope claims. CVE-2026-32727 affects the SciTokens reference library before version 1.9.7, where the Enforcer component normalized both the authorized path and requested path and then compared them with a startswith check, allowing .. sequences in a token scope to escape the intended directory restriction. The issue is classified as CWE-22 and carries a CVSS v3.1 score vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.
A related flaw, CVE-2026-32725, affects scitokens-cpp before version 1.4.1 and similarly allows authorization bypass through improper handling of path-based scopes. In that library, .. path components were collapsed during normalization instead of being rejected, enabling parent-directory traversal that broadened access beyond the permitted path. The vulnerability is tracked as CWE-23 with CVSS v3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L, and both issues were addressed in their respective patched releases.
See affected versions and whether adversaries are exploiting it.
5 events from the most recent confirmed update back to the earliest known activity.
GitHub security advisories received the new CVE-2026-32727 entry for the SciTokens reference library on March 31, 2026. The vulnerability affects versions prior to 1.9.7 and stems from path normalization combined with a startswith-based scope check.
A new CVE, CVE-2026-32726, was disclosed for scitokens-cpp versions prior to 1.4.1, describing an authorization bypass caused by prefix-based path scope validation that failed to enforce path-segment boundaries. The flaw could let a token authorized for one path access sibling paths with the same prefix, and it was remediated in version 1.4.1.
A new CVE, CVE-2026-32725, was disclosed for scitokens-cpp, describing an authorization bypass caused by improper handling of path-based scopes in versions before 1.4.1. The issue was classified as CWE-23 with high confidentiality and integrity impact.
The SciTokens reference library fixed an authorization bypass vulnerability in version 1.9.7. The issue in the Enforcer component allowed attackers to use '..' sequences in a token's scope claim to escape intended directory restrictions during path validation.
A relative path traversal vulnerability affecting scitokens-cpp versions prior to 1.4.1 was remediated in release 1.4.1. The flaw allowed authorization bypass by using '..' path components in token scope claims to expand access beyond the intended directory.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Two high-severity path traversal vulnerabilities in **SillyTavern** allow authenticated attackers to access files outside intended chat directories in versions prior to `1.17.0`. **CVE-2026-34522** affects the `/api/chats/import` endpoint and lets an attacker write arbitrary files by injecting traversal sequences into the `character_name` parameter, creating a risk of unauthorized file modification and service disruption. The flaw carries a CVSS v3.1 rating of `AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`. A second flaw, **CVE-2026-34524**, affects `/api/chats/export` and `/api/chats/delete`, where supplying `avatar_url=".."` can enable arbitrary file read and delete operations within the application's user data root. The issue could expose or destroy sensitive files including **`secrets.json`** and **`settings.json`**, with a CVSS v3.1 vector of `AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`. Both vulnerabilities are classified as **CWE-22 path traversal** issues and were patched in **SillyTavern `1.17.0`**.
Jun 29, 2026
Multiple newly disclosed vulnerabilities exposed **arbitrary file write** paths through symlink handling and path validation failures in developer and server-side software. In **Crawl4AI** before `0.8.8`, `CVE-2026-56258` affects screenshot and PDF endpoints by combining weak `output_path` validation, symlink following, and a **TOCTOU** race, allowing unauthenticated remote attackers to write files outside the intended directory and potentially reach code execution. In **Cursor Desktop** before `3.0`, `CVE-2026-50549` lets a malicious agent escape the workspace sandbox by forcing path canonicalization to fail and then abusing an in-workspace symlink to write arbitrary files under the user’s privileges, including paths that could enable later unsandboxed execution. A related pattern also appeared in archive extraction and privileged upload handling. The **extract-zip** package is affected by `CVE-2026-56876`, which fails to validate symlink targets inside ZIP archives, enabling path traversal outside the extraction directory and possible arbitrary file read or write when processing untrusted archives. Separately, **pwnlift** disclosed `CVE-2026-56815` in a privileged upload handler that could be abused for arbitrary file write **as root** through direct symlink following and a TOCTOU race; an initial fix was bypassable before a follow-up patch was merged, while one downstream deployment mitigated exposure by removing the privileged `sudo` entry. Together, the disclosures highlight recurring risk from incomplete path canonicalization, unsafe symlink handling, and containment checks in file-write workflows.
Jul 2, 2026
GitLab disclosed and remediated three high-severity vulnerabilities in GitLab CE/EE that could be exploited by unauthenticated attackers under certain conditions. **CVE-2026-4922** is a cross-site request forgery flaw (`CWE-352`) that could let an attacker trigger GraphQL mutations as an authenticated user, while **CVE-2026-5262** is a cross-site scripting issue (`CWE-79`) that could expose tokens in the Storybook development environment. GitLab also fixed **CVE-2026-5816**, an improper path validation flaw (`CWE-41`) that could allow arbitrary JavaScript execution in a victim’s browser session. The issues affect multiple GitLab CE/EE release lines, with patched versions identified as **18.9.6**, **18.10.4**, and **18.11.1** depending on the flaw. CVE-2026-4922 affects versions from `17.0` before `18.9.6`, `18.10` before `18.10.4`, and `18.11` before `18.11.1`; CVE-2026-5262 affects versions from `16.1.0` before `18.9.6`, `18.10` before `18.10.4`, and `18.11` before `18.11.1`; and CVE-2026-5816 affects `18.10` before `18.10.4` and `18.11` before `18.11.1`. The vulnerabilities carry CVSS v3.1 ratings reflecting high confidentiality and integrity impact, and GitLab linked the disclosures to its patch release notice, internal work items, and HackerOne reports.
Jun 29, 2026