Advisory

RUSTSEC-2026-0277

Also known as: GHSA-72g6-wgrg-vhm7, RUSTSEC-2026-0276

Summary

Path traversal in apimock-server's file-serving fallback

Details

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.

Exposure depends on the bind address. The default is 127.0.0.1;
deployments binding 0.0.0.0 or a LAN address are reachable from the
network. Most HTTP clients normalise .. away before sending, so
reaching it requires a client that does not.

All published versions before 5.19.1 are affected. Fixed in 5.19.1 by
canonicalising each resolved path and rejecting anything outside its
base directory.

This advisory also covers `apimock` 5.x, which depends on
apimock-server. apimock 4.x predates the crate split and carries its
own advisory for the same issue, fixed in 4.8.1.

Severity

Not rated by the source.

Dates

Published
2026-08-26 12:00 UTC
Modified
2026-09-02 09:10 UTC

Affected packages and fixes

apimock-server

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 5.19.1 (semver)

Fixed versions

5.19.1

Fix

  • Fixed version 5.19.1
    cargo update -p apimock-server --precise 5.19.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences