rust

2 tools · 1 release line

The Rust compiler and package manager. Each tool carries its own sandbox boundary — they are not the same.

boks cargo

boks rustc

Source ↗ Registry ↗

Release lines we maintain · the project decides these

findings shown are the whole project at that line

Tag Resolves to Lifecycle Updated Findings What the tag promises

latest 1.98.0 stable 2026-08-21

tracks the newest supported release

stable — floats, carries security updates
unstable — tracks pre-releases, may break
eol — frozen, upstream is done

Tools in this project · pick one to inspect

capabilities differ between them

Tool Capabilities Seccomp Findings Image Description

cargo netrw default clean rust-cargo The Rust package manager and build tool rustc rw default

M2L3

rust-rustc The Rust compiler

showing cargo rustc from rust@latest → 1.98.0 stable

Findings

clean

identical on amd64, arm64 — one table describes both

No known findings in this image at the last scan.

These are the findings of rust-cargo, which ships cargo. Other tools in this project ship in different images and carry different findings. boks reports and gates; it never edits an image to clear a finding.

Findings

M2L3

identical on amd64, arm64 — one table describes both

CVE Sev CVSS Affects Description

GHSA-vfvv-c25p-m7mm ↗ M 6.9 rkyv rkyv: Panic safety bugs in `InlineVec::clear` and `SerVec::clear` enable arbitrary code execution

GHSA-j39j-6gw9-jw6h ↗ L 2.7 git2 git2 has potential undefined behavior when dereferencing Buf struct

GHSA-xwfj-jgwm-7wp5 ↗ L 2.3 tracing-subscriber Tracing logging user input may result in poisoning logs with ANSI escape sequences

GHSA-3pv8-6f4r-ffg2 ↗ M — tar tar has a PAX header desynchronization issue

GHSA-cq8v-f236-94qc ↗ L — rand Rand is unsound with a custom logger using rand::rng()

1 further advisory matched this image and was assessed not to apply to it — see the VEX document for the reasoning and the evidence

CVE Affects Assessed

CVE-2026-27171 zlib not affected · vex

These are the findings of rust-rustc, which ships rustc. Other tools in this project ship in different images and carry different findings. boks reports and gates; it never edits an image to clear a finding.

Composition

default + binutils, cc, rustc

runtime none — self-contained

composes binutils, cc, rustc

Some tools are only useful composed: a pip-installed CLI needs python as its runtime, bash pulls in coreutils. boks resolves that for you — -e git,python:flake8 composes explicitly.

Composition

default nothing — stands alone

runtime binutils, cc

composes binutils, cc

Some tools are only useful composed: a pip-installed CLI needs python as its runtime, bash pulls in coreutils. boks resolves that for you — -e git,python:flake8 composes explicitly.

Image

image ghcr.io/boks-sh/rust-cargo:1.98.0

digest

platforms

size 34 MB unpacked · 1 layer

base scratch

signed cosign · verified

last scan 2026-08-21

Image

image ghcr.io/boks-sh/rust-rustc:1.98.0

digest

platforms

size 480 MB unpacked · 1 layer

base scratch

signed cosign · verified

last scan 2026-08-21

Sandbox boundary

cargo

capabilities

netrw

Filled is granted by default; the rest need --cap at the point of use.

seccomp tier

per tool

default

The syscall filter applied to this tool's entry point. Tools sharing an image do not share a tier.

dotfiles mapped in

read-only unless noted

~/.cargo/registry · writable

env passed through

0 of 1

Nothing else crosses in. No AWS_*, no SSH_AUTH_SOCK unless you ask.

per-subcommand

no overrides

Every invocation gets the same boundary. Where a tool needs more for one subcommand only, boks scopes it there rather than granting it everywhere.