NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

CVE-2026-62336 — agent

Fix: qbee-io/qbee-agent@0fdf8e4

CVE-2026-62336 is a Path Traversal vulnerability in go.qbee.io/agent. A fix is available for go.qbee.io/agent — see the affected versions and patch details below.

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

Also known asGHSA-xhv5-8fpq-g7hf
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 17, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹go.qbee.io/agent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogo.qbee.io/agentall versions0.0.0-20260615134032-0fdf8e411de5go get go.qbee.io/agent@v0.0.0-20260615134032-0fdf8e411de5

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.qbee.io/agent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update go.qbee.io/agent to 0.0.0-20260615134032-0fdf8e411de5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-62336 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

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 n
O3 Security · Impact-Aware SCA

Is CVE-2026-62336 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2026-62336: agent Path Traversal — Fix Available