Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Race Condition Enabling Link Following and Time-of-check Time-of-use (TOCTOU) Race Condition in remove_dir_all

GHSA-mc8h-8q98-g5hr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (remove_dir_all 0.8.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

The removedirall crate is a Rust library that offers additional features over the Rust standard library fs::removedirall function. It suffers the same class of failure as the code it was layering over: TOCTOU race conditions, with the ability to cause arbitrary paths to be deleted by substituting a symlink for a path after the type of the path was checked. Thanks to the Rust security team for identifying the problem and alerting us to it.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-mc8h-8q98-g5hr

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-mc8h-8q98-g5hr

Advisory: Race Condition Enabling Link Following and Time-of-check Time-of-use (TOCTOU) Race Condition in remove_dir_all
IDs: GHSA-mc8h-8q98-g5hr
Record: https://patchnext.com/advisories/ghsa-mc8h-8q98-g5hr (revision 1, source checked 26 Oct 2026, 15:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: remove_dir_all 0.8.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io remove_dir_all: affected < 0.8.0; fixed in 0.8.0

## Suggested inspection (read-only)
- crates.io remove_dir_all: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on remove_dir_all.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mc8h-8q98-g5hr (GitHub-reviewed advisory GHSA-mc8h-8q98-g5hr lists affected ranges: crates.io remove_dir_all >=0 <0.8.0)

Commands are suggestions: review each one before running it.

Loading voting…