EUVD-2026-86455
GHSA-pmh4-7cvf-mhhx
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-privilege access to littrs-backed app
-
ExploitSupply traversal string in Sandbox::mount `relative` arg
-
ExecutionResolve mount path outside sandbox root
-
ImpactRead or write files beyond confinement
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an application built on littrs 0.6.1 or 0.6.2 that routes attacker-influenced input into the |
| Impact | This is a low-priority issue despite being a remotely exploitable path traversal. The VulDB CVSS 4.0 base score of 2.1 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L) reflects only low confidentiality, integrity, and availability impact and requires some level of privilege (PR:L) to invoke the vulnerable Sandbox::mount API - signals that all point to modest real-world risk. SSVC-style reading: exploitation status is 'proof-of-concept' (VulDB E:P) with a publicly disclosed exploit, but there is NO CISA KEV listing and NO EPSS score provided, so there is no evidence of active or automatable exploitation. The score is disputable: because Sandbox::mount is a library function invoked in-process rather than a network-listening service, the AV:N (network) rating is questionable and likely overstates reach - a local/config API vector (AV:L) is more defensible, though a sandbox-escape via path traversal could arguably justify higher integrity impact than VulDB assigned. The dominant caveat is source quality: this is a single-source, low-signal VulDB entry with a non-responsive vendor and no confirmed fix, so affected-version and impact details are not independently corroborated. |
| Exploit ScenarioDerived | An application embeds littrs 0.6.1/0.6.2 and passes untrusted input into the |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 24, 2026
Path traversal in the littrs Rust sandboxing library (versions 0.6.1 and 0.6.2) allows the relative argument passed to Sandbox::mount in crates/littrs/src/lib.rs to escape the intended sandbox mount point and reach files outside it. The flaw is not directly reachable by anonymous internet users: it requires an application built on littrs that routes attacker-influenced input into the mount path, and the independent assessment rates the attack vector as local with low privileges required (CVSS:3.1 AV:L/AC:L/PR:L/UI:N, C:L/I:L/A:L), even though the CNA's CVSS 4.0 vector (AV:N, CVSS 2.1) frames it as remotely performable. Publicly available exploit code exists, and the vendor was contacted but did not respond; no fixed release has been published, so risk is confined to deployments that actually feed untrusted values into Sandbox::mount.
RemediationAI
No vendor-released patch was identified at time of analysis, and the vendor did not respond to early disclosure, so there is no fixed littrs version to upgrade to; monitor https://github.com/chonkie-inc/littrs/security/advisories/GHSA-j65r-rjxh-fgc4 and the upstream repository for a patched release. Until then, mitigation must live in the integrating application: canonicalize the relative value with std::fs::canonicalize (or the equivalent path-normalization routine) and reject any result that does not retain the intended sandbox root as a strict path prefix, explicitly refusing absolute paths, .. segments, and symlink components before calling Sandbox::mount - the trade-off is that legitimate mount paths containing symlinks or .. will break and must be normalized by the caller instead. Where the mount path can only ever be a fixed, trusted constant, hard-code it and remove the untrusted parameter from the call site entirely; this eliminates the flaw with no runtime cost. As a compensating control, run the hosting process with least privilege and confine it with OS-level isolation (container, seccomp, or AppArmor/SELinux profile) so that a successful traversal reaches only a deliberately restricted directory, accepting the added operational complexity and potential breakage of legitimate file access as the cost. Note that both known affected versions, 0.6.1 and 0.6.2, carry the flaw, so downgrading to an earlier release is not a confirmed remediation path.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
littrs is a Rust crate providing a sandbox abstraction; the affected unit is the Sandbox::mount function in crates/littrs/src/lib.rs, which accepts a relative path argument used to resolve a mount location. Because the value is not adequately constrained against traversal sequences and relative-path escapes, it falls into CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), the classic root-cause class where user-supplied path components such as ../ are joined to a base directory without canonicalization or an enforced prefix check. The practical consequence is that the effective mount target can resolve outside the sandbox root, granting the caller read and write access to host paths the sandbox was meant to isolate. No CPE strings were supplied in the intelligence feed, but the affected artifacts are explicitly the littrs 0.6.1 and 0.6.2 crate releases. The impact ceiling is bounded by the privilege level of the process performing the mount and by whether the integrating application ever exposes the relative parameter to untrusted input.
Know when Rust gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Sandbox::mount is an in-process library API so AV:L and PR:L (caller must reach it with some privilege); path traversal yields limited out-of-sandbox read/write, so C/I/A each Low.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
DescriptionCVE.org
A vulnerability was determined in chonkie-inc littrs 0.6.1/0.6.2. Impacted is the function Sandbox::mount of the file crates/littrs/src/lib.rs. Executing a manipulation of the argument relative can lead to path traversal. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Command injection via Windows CreateProcess argument parsing affects multiple language runtimes and tooling (Node.js, PH
In the standard library in Rust before 1.52.0, a double free can occur in the Vec::from_iter function if freeing the ele
In the standard library in Rust before 1.52.0, the Zip implementation can report an incorrect size due to an integer ove
Stored cross-site scripting and open redirect in Warpgate's SSO endpoints (versions prior to 0.25.5) allow an unauthenti
library/std/src/net/parser.rs in Rust before 1.53.0 does not properly consider extraneous zero characters at the beginni
Denial of service in the Vector observability pipeline's `logstash` source (versions 0.15.0 through 0.56.x) allows a rem
The Rust Programming Language Standard Library 1.34.x before 1.34.2 contains a stabilized method which, if overridden, c
In the standard library in Rust before 1.52.0, the Zip implementation calls __iterator_get_unchecked() more than once fo
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe c
Cargo prior to Rust 1.26.0 may download the wrong dependency if your package.toml file uses the `package` configuration
Rust is a programming language. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable, no auth
The Rust Programming Language Standard Library version 1.29.0, 1.28.0, 1.27.2, 1.27.1, 127.0, 126.2, 126.1, 126.0 contai
Exploit-DB