Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-2m67-cxxq-c3h8

HighCVSS 8.8 / 10
Published Mar 12, 2026·Last modified Mar 14, 2026
Affected Components(0)

No affected components available

Description

Summary

Workspace boundary enforcement currently has three related bypass risks. This issue tracks fixing all three in one pull request.

Details

R1 - Dangling Symlink Component Bypass

  • What happens: Path validation can miss dangling symlink components during traversal checks.
  • Why it matters: A symlink that is unresolved at validation time can later resolve to an external location.
  • Impact: Read and write operations may escape workspace boundaries.
  • Affected area: src/security/path.rs (check_symlink_escape).

R2 - TOCTOU Between Validation and Use

  • What happens: The path is validated first, then used later for filesystem operations.
  • Why it matters: A concurrent filesystem change can swap path components after validation but before open/write.
  • Impact: Race-based workspace escape is possible.
  • Affected area: Filesystem and file-consuming tools that call validate_path_in_workspace before I/O.

R3 - Hardlink Alias Bypass

  • What happens: A file inside workspace can be a hardlink to an inode outside the intended workspace trust boundary.
  • Why it matters: Prefix and symlink checks can pass while data access still mutates or reads external content.
  • Impact: Policy bypass for read/write operations.
  • Affected area: Any tool that reads or writes via validated paths.

Risk Matrix

| ID | Risk | Severity | Likelihood | Impact | |---|---|---|---|---| | R1 | Dangling symlink component bypass | High | Medium | Workspace boundary escape for read/write | | R2 | Validate/use TOCTOU race | High | Medium | Race-based boundary escape during file I/O | | R3 | Hardlink alias bypass | Medium | Low-Medium | External inode read/write through in-workspace path |

PoC

R1 - Dangling symlink component bypass

  1. Create a symlink inside workspace pointing to a missing target.
  2. Validate a path traversing that symlink.
  3. Create the target directory outside workspace after validation.
  4. Perform file operation and observe potential boundary escape if not fail-closed.

R2 - TOCTOU between validation and use

  1. Validate a candidate in-workspace path.
  2. Before open/write, replace an intermediate component with a link to external location.
  3. Continue with the file operation.
  4. Observe boundary escape if operation trusts only stale validation result.

R3 - Hardlink alias bypass

  1. Place a hardlink inside workspace that points to an external inode.
  2. Validate the in-workspace hardlink path.
  3. Read or write through this path.
  4. Observe external inode access through a path that appears in-scope.

Impacts

Unauthorized cross path boundary

Credit

@zpbrent

Patch

f50c17e11ae3e2d40c96730abac41974ef2ee2a8

Risk Scores
Base Score
8.8

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability.

Threat Intelligence
8.0

Exploitation activity has been observed. Apply available patches or mitigations urgently.

EPSS
0.62%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

High severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard