CVE-2026-129237 qbee-agent: Docker Compose build context Zip Slip writes outside context directory
A less-privileged Docker Compose context supplier can write files outside the extraction directory with qbee-agent privileges; qbee-agent deployments using Docker Compose should care.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- Available
What is CVE-2026-129237?
CVE-2026-129237 is a medium-severity path traversal vulnerability in qbee-io qbee-agent, published on 16 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
qbee-agent is the device agent component of the qbee.io IoT device management platform. Prior to 2026.41, the unpackTar extraction logic in app/utils/tar.go validates cleaned archive entry paths with strings.HasPrefix(targetPath, destdirClean) without enforcing a path-separator boundary. When UseContext enables the Docker Compose build context path in app/configuration/bundle_docker_compose.go, a less-privileged archive supplier with delegated configuration and/or file-manager access can provide a sibling-prefix traversal entry that passes the check, causing utils.UnpackTar to create directories and regular files outside the intended context extraction directory with qbee-agent process privileges, despite the supplier lacking authority to write those sibling files. In deployments where only full device or fleet administrators can provide Docker Compose context archives, this behavior is hardening rather than a crossed security boundary. The demonstrated impact is limited to nearby cache or project paths sharing the destination prefix, may affect integrity or availability of qbee-agent-managed Docker Compose state, and does not establish arbitrary absolute-path writes or direct code execution. This issue is fixed in version 2026.41.
Weakness: CWE-22
Which versions are affected by CVE-2026-129237?
1 open source package ship an affected version, including go.qbee.io/agent.
Only installations with a non-default setting turned on are exposed.
| Package | Affected | Fixed in |
|---|---|---|
go.qbee.io/agent Gopkg:golang/go.qbee.io/agent | All versions | 0.0.0-20260908095235-eb7875f0a849 |
Status by vendor (1)
| Who | Release | Status | Packages |
|---|---|---|---|
| Upstream | fixed | go.qbee.io/agent (0.0.0-20260908095235-eb7875f0a849) |
How do I fix CVE-2026-129237?
Upgrade go.qbee.io/agent to 0.0.0-20260908095235-eb7875f0a849 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-129237 being exploited?
There is no known exploitation of CVE-2026-129237 in the wild and no public exploit code.
Sources
Also known as GHSA-vx32-xf7g-9ghr.