Skip to content
OpenAdvisories
Unscored GHSA-72g6-wgrg-vhm7 RUSTSEC-2026-0276RUSTSEC-2026-0277

Path traversal in apimock's file-serving fallback

Published Aug 26, 2026 · Updated Sep 2, 2026 · Assigned by RUSTSEC

Description

The file-serving fallback joined a request-derived path onto the
configured response directory and checked only that the result existed,
never that it stayed inside that directory. A request containing a raw
`..` segment could read any file readable by the process, returned with
HTTP 200.

Read-only: no write, no code execution.

On the 4.x line `apimock` is a single crate containing the serving code.
Fixed in 4.8.1 by canonicalising each resolved path and rejecting
anything outside its base directory.

**apimock 5.0.0 and later are not affected by this advisory.** From
5.0.0 the serving code moved to the `apimock-server` crate, which
`apimock` depends on; that crate carries its own advisory for the same
issue, fixed in 5.19.1.

Affected packages

EcosystemPackageAffectedFixedRecord
crates.io apimock >= 0.0.0-0, < 4.8.1 · >= 5.0.0, < 5.0.0 4.8.1, 5.0.0 RUSTSEC-2026-0276
crates.io apimock-server >= 0.0.0-0, < 5.19.1 5.19.1 RUSTSEC-2026-0277

References