CVE
qbee-agent local privilege escalation in createFile helper
Affects qbee-agent setups where a file-distribution or template destination sits under a directory owned by an unprivileged user. Fixed in 2026.27.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.27
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The user's account is managed by the SSH Keys bundle. Devices use RAUC download mode. fs.protected_symlinks is disabled (0) for the RAUC /tmp path variant. A file-distribution or template destination is configured under a directory owned by an unprivileged user.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The qbee-io qbee-agent device agent has a flaw in its privileged createFile helper, which follows attacker-controlled symbolic links during file creation. A local user with low privileges and no required user interaction can use this to gain root access, modify arbitrary files, or cause a denial of service.
Original description
qbee-agent is the device agent component of the qbee.io IoT device management platform. Prior to 2026.27, the privileged createFile helper followed attacker-controlled symbolic links during file creation. A local unprivileged user whose account is managed by the SSH Keys bundle could replace ~/.ssh with a link to /root/.ssh, causing the agent to write an authorized key for root. On systems using RAUC download mode with ineffective kernel symlink protection, the predictable /tmp/.bundle.raucb.part path could be linked to a system file and then overwritten or truncated during an update. A file-distribution destination beneath an attacker-controlled directory could similarly redirect the partial-download path so the agent changed ownership of a sensitive file. These vectors could result in root privilege escalation, arbitrary file modification, or denial of service. This issue is fixed in version 2026.27.
Who should check
Teams running qbee-agent before 2026.27 on managed devices that use the SSH Keys bundle, RAUC download mode, or file distribution to unprivileged-owned directories.
Not fixed by: Setting fs.protected_symlinks=1 does not fix the home directory vector.
“Any managed device running qbee-agent up to the affected versions.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The user's account is managed by the SSH Keys bundle. Devices use RAUC download mode. fs.protected_symlinks is disabled (0) for the RAUC /tmp path variant. A file-distribution or template destination is configured under a directory owned by an unprivileged user.Upgrade to a fixed version: 2026.27.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-62336 (qbee-agent: Local Privilege Escalation and Arbitrary File Tampering via Symlink Following in createFile helper), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-62336 (entry last updated 2026-11-16):
Affected:
- qbee-io qbee-agent: fixed in 2026.27
Fixed versions: 2026.27.
Conditions (all must be true for the bug to be hit):
- The user's account is managed by the SSH Keys bundle. (source: https://github.com/qbee-io/qbee-agent/security/advisories/GHSA-xhv5-8fpq-g7hf)
- Devices use RAUC download mode. (source: https://github.com/qbee-io/qbee-agent/security/advisories/GHSA-xhv5-8fpq-g7hf)
- fs.protected_symlinks is disabled (0) for the RAUC /tmp path variant. (source: https://github.com/qbee-io/qbee-agent/security/advisories/GHSA-xhv5-8fpq-g7hf)
- A file-distribution or template destination is configured under a directory owned by an unprivileged user. (source: https://github.com/qbee-io/qbee-agent/security/advisories/GHSA-xhv5-8fpq-g7hf)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-62336 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62336 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/qbee-io/qbee-agent/security/advisories/GHSA-xhv5-8fpq-g7hf
- https://github.com/qbee-io/qbee-agent/pull/131
- https://github.com/qbee-io/qbee-agent/commit/0fdf8e411de5d0c142ae2590cf1c54bdfc2e529a
- https://github.com/qbee-io/qbee-agent/releases/tag/2026.27
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-62336
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-62336"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- qbee-io qbee-agent
fixed in 2026.27
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-62336
Is CVE-2026-62336 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The createFile helper in qbee-agent follows symbolic links, so a local unprivileged user can redirect a write to another file and tamper with it, which the advisory links to local privilege escalation.Source: github.com
Which versions are affected by CVE-2026-62336?
qbee-agent: before 2026.27.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 2026.27 are listed as affected. The advisory's conditions are a file-distribution or template destination under a directory owned by an unprivileged user, and, for RAUC download mode with the /tmp path variant, fs.protected_symlinks set to 0 (check with sysctl fs.protected_symlinks) and the user's account managed by the SSH Keys bundle.Source: github.com
How do I fix CVE-2026-62336?
Upgrade qbee-agent to 2026.27, the listed fixed version.Source: github.com