CVE-2026-27806

The Orbit agent's FileVault disk encryption key rotation flow on collects a local user's password via a GUI dialog and interpolates it directly into a Tcl/expect script executed via exec.Command("expect", "-c", script). Because the password is inserted into Tcl brace-quoted send {%s}, a password containing } terminates the literal and injects arbitrary Tcl commands. Since Orbit runs as root, this allows a local unprivileged user to escalate to root privileges.

CWE

• CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
• CWE-94: Improper Control of Generation of Code ('Code Injection')

Credit

This vulnerability was discovered and reported by bugbunny.ai.

• Local privilege escalation to root: Any unprivileged local user on a managed endpoint can execute arbitrary commands as root

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2026-27806 has a CVSS score of 7.8 (High). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.81.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-27806? CVE-2026-27806 is a high-severity OS command injection vulnerability in github.com/fleetdm/fleet/v4 (go), affecting versions < 4.81.1. It is fixed in 4.81.1. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2026-27806? CVE-2026-27806 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/fleetdm/fleet/v4 are affected by CVE-2026-27806? github.com/fleetdm/fleet/v4 (go) versions < 4.81.1 is affected.
4. Is there a fix for CVE-2026-27806? Yes. CVE-2026-27806 is fixed in 4.81.1. Upgrade to this version or later.
5. Is CVE-2026-27806 exploitable, and should I be worried? Whether CVE-2026-27806 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-27806 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-27806? Upgrade github.com/fleetdm/fleet/v4 to 4.81.1 or later.