Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61670 medium CVSS 6.5

Vulnerability in microsandbox (CVE-2026-61670)

Summary

Vulnerability in microsandbox (CVE-2026-61670). Confidential information can be exposed externally. Exploitable via NetworkConfig. Mitigation: upgrade to 0.5.10 or later.

Original description

The description as published by the source.

Summary

When the SDK spawns a sandbox, the msb sandbox child process receives the full network configuration as an inline --network-config 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//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:

let net_json = serde_json::to_string(&config.network)
     .expect("failed to serialize network config");
args.push(OsString::from("--network-config"));
args.push(OsString::from(net_json));   // secrets land in argv here

The CLI accepts it only as an inline string and parses it with serde_json::from_str, so there is no off-argv channel today. The field is declared at crates/cli/lib/sandbox_cmd.rs line 152 and parsed near line 234:

/// Network configuration as JSON.
pub network_config: Option,…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61670 has been found in microsandbox.
Attackers can target a specific entry point like NetworkConfig over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade microsandbox to 0.5.10 or later.
If unsure, ask your IT team or search "microsandbox CVE-2026-61670" on the vendor's site.

CVE-2026-61670 (microsandbox) — CWE-214 / CVSS v3 6.5
Attack vector: local / no user interaction
Attack surface: NetworkConfig / spawn.rs / env
Patched: 0.5.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-214) exists in microsandbox. Attackers reach the vulnerable code path via NetworkConfig.

📍 Affected scope

Check the vendor advisory for the affected versions of microsandbox. Attack surface: NetworkConfig / spawn.rs / env.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.5.10.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'microsandbox' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'microsandbox' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で microsandbox を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade microsandbox to 0.5.10

    ステージング環境で 0.5.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rust microsandbox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.10"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details