CVE-2026-27806
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFleet is open source device management software. Prior to 4.81.1, 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. This vulnerability is fixed in 4.81.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Orbit agent's FileVault key rotation flow collects a user's password via GUI and interpolates it directly into a Tcl/expect script using exec.Command. Since the password is inserted into Tcl brace-quoted send {%s}, a password containing '}' terminates the literal and injects arbitrary Tcl commands. Because Orbit runs as root, a local unprivileged user can achieve root privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.81.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Fleet Orbit installationRun 'fleetctl get orbits' or check for Orbit binary at /usr/local/bin/orbit or review installed packagesAffected if Fleet Orbit agent is present on the system
-
Determine Fleet versionRun 'fleetctl --version' or 'orbit --version' to obtain the installed version numberAffected if Version is lower than 4.81.1 (e.g., 4.81.0, 4.80.x, etc.)
-
Check if FileVault key rotation is configuredReview Fleet configuration for FileVault disk encryption settings, or inspect orbit logs for 'FileVault' or 'key rotation' activityAffected if FileVault key rotation flow is enabled or has been used on this host
-
Verify Orbit runs as rootCheck the Orbit service/process owner: 'ps aux | grep orbit' or inspect the service file at /Library/LaunchDaemons/com.fleetdm.orbit.plistAffected if Orbit process runs under root (UID 0)
-
Confirm password input methodExamine orbit configuration for MDM-derived or manually entered passwords in the FileVault key rotation workflowAffected if User passwords are collected locally via GUI for FileVault rotation rather than retrieved from MDM
You are affected if Fleet Orbit is installed with version below 4.81.1 AND FileVault key rotation is configured to accept user-provided passwords locally.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.81.1
Upgrade Orbit agent to version 4.81.1 or later, which contains the fix for proper input sanitization before interpolation into Tcl scripts.
Fleet 4.81.1
- 1. Identify all systems running Fleet Orbit agent with version less than 4.81.1
- 2. Upgrade the Fleet server to version 4.81.1 or later
- 3. Ensure the Orbit agent is updated to the corresponding version (4.81.1 or later) on all managed devices
- 4. Verify the upgrade was successful by checking the Orbit agent version (fleetctl orbit or via Fleet UI)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27806 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data