{"answers":{"affected":"2 open source packages ship an affected version, including microsandbox.","exploited":"There is no known exploitation of CVE-2026-61670 in the wild and no public exploit code.","fix":"Upgrade microsandbox to 0.5.10 or later.","what":"CVE-2026-61670 is a medium-severity vulnerability in superradcompany microsandbox, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-61670 and fix it if it is affected.\n\nWhat it is: CVE-2026-61670 is a medium-severity vulnerability in superradcompany microsandbox, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-61670 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- microsandbox (crates.io): affected all versions; fixed in 0.5.10\n- microsandbox (crates.io): affected all versions; fixed in 0.5.10\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-61670/ (Markdown: https://insights.sbomify.com/CVE-2026-61670/index.md)","id":"CVE-2026-61670","markdown":"https://insights.sbomify.com/CVE-2026-61670/index.md","name":"CVE-2026-61670","record":{"aliases":["GHSA-m8f5-rh7h-vgg3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"microVM runtime library","requires_auth":"low_privilege","summary":"Local attackers can read secret API keys and tokens from process arguments in microsandbox, exposing sensitive data on shared hosts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-214","name":"Invocation of Process Using Visible Sensitive Information"}],"description":"microsandbox is an easy, fast, local-first microVM runtime and library. Prior to 0.5.10, sdk/rust/lib/runtime/spawn.rs serializes NetworkConfig secret values into the --network-config argument and passes per-sandbox secrets through repeated --env arguments accepted by crates/cli/lib/sandbox_cmd.rs. Other local users or co-resident processes can read these values through the host process table, including /proc process command lines on Linux and process listings on Linux and macOS, for the lifetime of the sandbox. Exploitation does not require code execution inside the sandbox or access to the spawning user's session, and can disclose host-side API keys, tokens, and environment secrets on shared hosts, CI runners, and developer systems. This issue is fixed in version 0.5.10.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"microsandbox: Secret values exposed in world-readable process arguments","id":"CVE-2026-61670","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":6,"next":{"headline":"WeGIA: Systemic IDOR + Missing CSRF — extract($_REQUEST) in All Controle Classes","id":"CVE-2026-61671"},"packages":[{"ecosystem":"crates.io","fixed":["0.5.10"],"introduced":["0"],"last_affected":[],"package":"microsandbox","purl":null,"source":"GHSA-m8f5-rh7h-vgg3"},{"ecosystem":"crates.io","fixed":["0.5.10"],"introduced":["0"],"last_affected":[],"package":"microsandbox","purl":"pkg:cargo/microsandbox","source":"GHSA-m8f5-rh7h-vgg3"}],"prev":{"headline":"DIRAC: Pilot code downloaded over unverified HTTPS connection","id":"CVE-2026-61668"},"products":["microsandbox"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["superradcompany"]},"summary":"Local attackers can read secret API keys and tokens from process arguments in microsandbox, exposing sensitive data on shared hosts.","url":"https://insights.sbomify.com/CVE-2026-61670/"}