Friday, 20 November 2026
2 agent hacks today▼ 9 vs yesterday (11)

Zip Slip flaw in qbee-agent writes files outside build context

A missing path separator check in the device management agent's tar extractor lets a Docker Compose build context archive drop files into neighbouring directories.

By The Agentic Times ·

A tar-striped ribbon unspools sideways, its contents spilling through a broken fence into adjacent garden plots instead of staying within marked boundaries.
A tar-striped ribbon unspools sideways, its contents spilling through a broken fence into adjacent garden plots instead of staying within marked boundaries. · Illustration: The Agentic Times

A path traversal flaw in qbee-agent, the device management agent from Qbee, allows a crafted Docker Compose build context archive to write files outside the directory it is supposed to be unpacked into, according to a GitHub security advisory published on 16 November 2026. The advisory is tracked as GHSA-vx32-xf7g-9ghr and CVE-2026-129237, and affects the Go module go.qbee.io/agent.

The problem is in the agent's tar extraction helper, in the file app/utils/tar.go. According to the advisory, the extractor builds the target path for each archive entry, then checks that it stays inside the destination directory using a simple string prefix test. That test does not require a path separator at the boundary. So if the destination directory is a path ending in "context", an archive entry such as "../context-outside/payload.txt" resolves to a sibling directory whose name begins with the same characters, and the check still passes. The agent then creates the directory and writes the file there.

This class of bug is known as Zip Slip, where an archive entry escapes the folder it is being unpacked into. In this case the escape is limited. The advisory is explicit that the proof of concept does not show writing to arbitrary locations such as /etc/passwd, because those paths do not share the destination prefix and are still rejected. What it does show is the ability to create directories and regular files in sibling paths, with the privileges of the qbee-agent process, and to corrupt or alter files in nearby Docker Compose cache and project directories whose cleaned paths share the prefix.

The route to the vulnerable code runs through Qbee's Docker Compose support. According to the advisory, the Docker Compose bundle downloads a build context archive and unpacks it into the compose project context directory using the same helper. That path is enabled when the UseContext option is set, and the context itself is a remote configuration field. The advisory says context archives are resolved either from local file:// sources or from the Qbee file manager API. Qbee's own documentation, cited in the advisory, lists "Build Context" as a Docker Compose configuration option.

The researcher who filed the advisory also set out when this counts as a security boundary rather than hardening. The argument is that Qbee's role based access control separates permission to manage configuration from permission to manage files, and Qbee's continuous integration documentation describes using a dedicated user restricted to configuration changes. Where a less privileged user or automated pipeline can supply a context archive, that supplier should not be able to write arbitrary sibling files in the agent's Docker Compose cache area. The advisory adds that if only full device or fleet administrators can supply context archives in a given deployment, the finding should be treated as hardening for that deployment.

Two failing regression tests were submitted as proof. One targets the extractor directly and records the payload being written outside the destination path. The second runs through the Docker Compose context code path and records a file written to a context-outside directory inside the compose project cache. Code references were verified against a specific commit of the qbee-io/qbee-agent repository, the advisory says.

The advisory lists the issue as reported. It does not state a fixed version.

Sources

  1. github.comhttps://github.com/advisories/GHSA-vx32-xf7g-9ghr