GHSA-xhv5-8fpq-g7hf · go.qbee.io/agent
GHSA-xhv5-8fpq-g7hf · Reported 17 Nov 2026
Full advisory details, affected packages, severity context, and original source.
Affected technology
Affected versions and fixes
Version information comes from OSV, NVD, and the CVE vendor record. Each source may describe a different package, release branch, or platform.
go.qbee.io/agent · Go
OSV- All earlier versions · before 0.0.0-20260615134032-0fdf8e411de5 (exclusive)
Fixed releases / commits: 0.0.0-20260615134032-0fdf8e411de5
Advisory overview
This is a Local Privilege Escalation (LPE) vulnerability stemming from improper symlink handling (CWE-59: Link Following) and improper ownership management (CWE-282) inside the qbee-agent file manager logic. ### Impact Any managed device running qbee-agent up to the affected versions. The impact manifests in three distinct vectors: 1. **Primary Vector (Full Privilege Escalation to Root - Default Configuration)**: If an unprivileged user's account is managed by the SSH Keys bundle, they can replace or remove their own `~/.ssh` directory and create a symlink pointing to `/root/.ssh`. On the next configuration apply, qbee-agent follows the symlink and writes the user's server-provisioned public key directly into `/root/.ssh/authorized_keys`. Since the symlink resides inside the user's own home directory, kernel protections like `fs.protected_symlinks` do not block this execution. The attacker can then instantly log in as root via SSH. 2. **Secondary Vector (Arbitrary File Overwrite / DoS via RAUC Staging)**: On devices utilizing RAUC download mode, the agent uses a predictable, world-writable staging path (`/tmp/.bundle.raucb.part`). If `fs.protected_symlinks` is disabled `(0)`, an unprivileged user can symlink this path to a vital system file (e.g., `/etc/shadow` or `/etc/pam.d/*`), causing the agent to truncate or overwrite it with server-supplied update data during a RAUC update deployment. 3. **Tertiary Vector (Arbitrary File Re-ownership via File Distribution)**: If an operator configures a file-distribution/template destination under a directory owned by an unprivileged user, the attacker can create a symlink at the partial download path targeting a sensitive system file. The agent will then inadvertently execute `file.Chown()` on the targeted file, handing ownership over to the unprivileged attacker. ### Patches The vulnerability has been addressed by hardening file creation and directory traversal inside `app/configuration/file_manager.go`. Specifically, the agent now enforces `syscall.O_NOFOLLOW` and proper existence validation flags during privileged operations to prevent link resolution outside intended directories. Users should upgrade to version 2026.27 (or newer) to fully mitigate these vectors. ### Workarounds If upgrading immediately is not feasible, administrators can apply the following mitigations: 1. Disable the SSH Keys Bundle: Temporarily turn off SSH key management within the Qbee platform for non-trusted local accounts to eliminate the primary privilege escalation vector. 2. Restrict Local Home Directory Alterations: Enforce strict file permissions or monitoring on managed user home directories to block unprivileged users from deleting or replacing ~/.ssh with a symbolic link. 3. Enable Kernel Symlink Protection: Ensure that system-level symlink protections are active to mitigate the secondary `/tmp` vector by verifying that the following sysctl parameter is set to 1 (though note this does not fix the primary home directory vector): ```bash sysctl -w fs.protected_symlinks=1 ```
Also known as
CVE-2026-62336
