VulnerabilityPublished 18 Sep 2026Updated 21 Sep 2026

CVE-2026-61670: superradcompany microsandbox · Invocation of Process Using Visible Sensitive Information

Affects superradcompany microsandboxSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.5.10 when convenient.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.5.10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade microsandbox and superradcompany/microsandbox to 0.5.10.

Affected software

Product	Affected	Fixed in
superradcompanymicrosandbox	Affected <0.5.10	Fixed in 0.5.10
GitHubsuperradcompany/microsandbox`pkg:github/superradcompany/microsandbox`Other threats	Affected <0.5.10	Fixed in 0.5.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade microsandbox to version 0.5.10 or later, where this issue is fixed. Prior to upgrading, be aware that secrets passed via command-line arguments may be exposed to other local users or processes. No other mitigation is indicated by the vendor advisory.

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.

Impact

The vulnerability allows local users or processes on the same host to read sensitive information such as API keys, tokens, and environment secrets from the command-line arguments of the microsandbox process. This can lead to unauthorized disclosure of secrets on shared environments like CI runners or multi-user developer systems. There is no impact on integrity or availability, and exploitation does not require code execution inside the sandbox or access to the spawning user's session.

Summary

In microsandbox versions before 0.5.10, the runtime serializes secret network configuration values and environment secrets into command-line arguments (--network-config and repeated --env arguments). These arguments are visible to other local users or co-resident processes through host process tables and process listings on Linux and macOS systems. This exposure allows disclosure of sensitive host-side API keys, tokens, and environment secrets on shared hosts, CI runners, and developer systems without requiring code execution inside the sandbox or session access. The vulnerability is classified as CWE-214 (Invocation of Process Using Visible Sensitive Information) and has a CVSS 3.1 score of 6.5 (medium severity). The issue is resolved in microsandbox version 0.5.10.

CWE-214Invocation of Process Using Visible Sensitive Information (opens in a new tab)
Base weakness
A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.2 (opens in a new tab)
V14.3.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Sep 2026, 04:11 UTC

WeaknessesCWE-214

Technical details

References

Community reviews

Related threats