Threat Intel

CVE-2026-79535: VoiceMode configuration becomes executable shell input

VoiceMode through 8.10.1 can execute injected configuration on service start. The optional config tools must be enabled to reach the MCP path.

Armor11 min read

Tracking: CVE-2026-79535
Severity: No CVSS severity assigned in the reviewed CVE record

Who is affected

VoiceMode through 8.10.1 when a caller can use update_config or voicemode config set. The maintainer says the config tools are optional and absent from the default MCP tool set.

How the attack works

Configuration values are written to ~/.voicemode/voicemode.env without safe shell quoting. The Whisper and serve startup scripts subsequently load that file using source, which evaluates embedded shell substitutions. The command runs on the next service start or reboot, with the service account's privileges.

This is delayed execution through configuration. A successful write may leave a payload waiting even if no suspicious process appeared at the time of the tool call.

What to do

  1. Upgrade to 8.10.2 or later. The fix safely quotes writes, rejects control characters, and changes startup scripts to parse values as data.
  2. Inspect existing configuration files before restarting services. The release notes say existing files are migrated to safe quoting on the next config set.
  3. Restrict configuration tools to trusted callers and investigate unexpected commands following service starts.

Sources

threat-intelcvecommand-injection

See what your own fleet is running

Armor1 discovers and risk-scores every MCP server, skill and tool your developers have connected. Free for personal use, no credit card.

Start Free