Skip to content

← Public intelligence

crates.io package

microsandbox

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5crates.ioAmendedPublished

    microsandbox: Secret values exposed in world-readable process arguments

    CVE-2026-61670 · GHSA-m8f5-rh7h-vgg3

    Affected
    • crates.io microsandbox < 0.5.10
    Fixed in
    0.5.10· Vendor fix available
    Issue
    When the SDK spawns a sandbox, the msb sandbox child process receives the full network configuration as an inline --network-config <json command-line argument, and any per-sandbox environment as repeated --env KEY=VALUE arguments. On Linux a process's arguments are world-readable via /proc/<pid/cmdline, and on both Linux and macOS they are visible to other local processes via ps. Because the network configuration carries the real secret values used for host-side secret substitution, any unprivileged local user (or any process running as a different user on the same host) can read those secrets directly out of the process listing for as long as the sandbox is running. This defeats the "secrets that can't leak" guarantee for the host side of the boundary. Details The SDK serializes the entire NetworkConfig, including the real (non-placeholder) secret values, and pushes it onto the child argv, in sdk/rust/lib/runtime/spawn.rs near line 1241: The CLI accepts it only as an inline…

    Recommended action: Upgrade to 0.5.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →