llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Go · go.qbee.io/agent

GHSA-XHV5-8FPQ-G7HF

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

Parche disponible
Descargar PNG JSON
CVSS
—
high
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versióncommit 0fdf8e4
Exposición2 dDesde la divulgación, 17 nov 2026, 3:48 p. m.
Detección33 minDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Monitoreo
Detectada +1
03:48 p. m.
04:00 p. m.
02:44 a. m.
03:48 p. m.
06:32 a. m.
09:16 p. m.
12:00 p. m.
02:44 a. m.
FechaFaseEventoDetalle
Divulgación Publicada GHSA-XHV5-8FPQ-G7HF divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

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.
  1. 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.
  1. 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.
  1. 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.
  1. 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
Versiones

Rangos afectados

Afectada Corregida
go.qbee.io/agent< 0.0.0-20260615134032-0fdf8e411de5
0.0.0-20260615134032-0fdf8e411de5
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Gogo.qbee.io/agent
Corregida commit 0fdf8e4 — —
Versiones corregidascommit 0fdf8e4
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-62336
Otrahttps://github.com/qbee-io/qbee-agent/security/advisories/GHSA-xhv5-8fpq-g7hf
Otrahttps://github.com/qbee-io/qbee-agent/pull/131
Otrahttps://github.com/qbee-io/qbee-agent/commit/0fdf8e411de5d0c142ae2590cf1c54bdfc2e529a
Otrahttps://github.com/qbee-io/qbee-agent
Otrahttps://github.com/qbee-io/qbee-agent/releases/tag/2026.27

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.