boks Index
Docs Releases

cargo

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
  • 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
showing cargo rustc from cargo@latest → 1.97.1 stable

Findings

H2M5L3

identical on amd64, arm64 — one table describes both

CVE Sev CVSS Affects Description
GHSA-xp3w-r5p5-63rr ↗ H 8.7 openssl rust-openssl has undefined behavior in X509Ref::ocsp_responders for certificates with non-UTF-8 OCSP URLs
GHSA-xphw-cqx3-667j ↗ H 7.3 thin-vec thin-vec: Use-After-Free and Double Free in IntoIter::drop When Element Drop Panics
GHSA-vfvv-c25p-m7mm ↗ M 6.9 rkyv rkyv: Panic safety bugs in `InlineVec::clear` and `SerVec::clear` enable arbitrary code execution
GHSA-3rjw-m598-pq24 ↗ M 5.5 cmov Cmov/CmovEq on aarch64 can produce wrong results if high-bits of registers are set
GHSA-phqj-4mhp-q6mq ↗ M 5.1 openssl rust-openssl: Potential out-of-bounds write in `CipherCtxRef::cipher_update_inplace` for AES-KW-PAD ciphers
GHSA-xv59-967r-8726 ↗ M 5.1 openssl rust-openssl vulnerable to heap buffer overflow when encrypting with AES key-wrap-with-padding
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 cargo, which ships every tool in this project. boks reports and gates; it never edits an image to clear a finding.

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.

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/cargo:1.97.1
digest
platforms
size 516 MB unpacked · 1 layer
base scratch
signed cosign · verified
last scan

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

none

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.

Sandbox boundary

rustc

capabilities

rw

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

none

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.

Provenance

sbom amd64 ↗ arm64 ↗
attestation amd64 ↗ arm64 ↗
scan report amd64 ↗ arm64 ↗ grype ·
vex amd64 ↗ arm64 ↗

Every image ships a full SBOM and a signed build attestation. Nothing here is a claim you have to take on trust.

10 findings across this project at latest. Counted once per advisory across every image the project builds.