go.qbee.io/agent
Affected
- introduced
0, fixed0.0.0-20260615134032-0fdf8e411de5(semver)
Fixed versions
0.0.0-20260615134032-0fdf8e411de5
Fix
- Fixed version
0.0.0-20260615134032-0fdf8e411de5go get go.qbee.io/[email protected]
Advisory
Also known as: CVE-2026-62336
qbee-agent: Local Privilege Escalation and Arbitrary File Tampering via Symlink Following in createFile helper
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:
~/.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./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.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:
/tmp vector by verifying that the following sysctl parameter is set to 1 (though note this does not fix the primary home directory vector):sysctl -w fs.protected_symlinks=1High Basis: The source's own band: HIGH
0, fixed 0.0.0-20260615134032-0fdf8e411de5 (semver)0.0.0-20260615134032-0fdf8e411de5
0.0.0-20260615134032-0fdf8e411de5go get go.qbee.io/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0