CVE-2026-62336: qbee-agent: Local Privilege Escalation and Arbitrary File Tampering via Symlink Following in createFile helper

High

OSV id
GHSA-xhv5-8fpq-g7hf
Also known as
CVE-2026-62336
Published
Last modified

Affected packages

PackageAffected versionsFixed in
go.qbee.io/agent
Go
< 0.0.0-20260615134032-0fdf8e411de5 0.0.0-20260615134032-0fdf8e411de5

How to fix it

Upgrade go.qbee.io/agent to 0.0.0-20260615134032-0fdf8e411de5 or later.

go get go.qbee.io/agent@v0.0.0-20260615134032-0fdf8e411de5
go mod tidy
  • Indirect Go modules are upgraded the same way (`go get module@version`).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

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):

sysctl -w fs.protected_symlinks=1

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.