CVE-2026-129237: qbee-agent: Docker Compose build context Zip Slip writes outside context directory

Published Nov 16, 2026
·
Updated

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/bundledockercompose.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.

Affected Software

1 affected component
qbee.io qbee-agent<2026.41

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade qbee-agent to a version that resolves this vulnerability.

    Fixed in 2026.41

Event History

Nov 16, 2026
CVE Published
via MITRE·04:52 PM
Data Sourced
via MITRE·04:52 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can realistically exploit this issue?

Exploitation requires a less-privileged user or principal that can supply Docker Compose build-context archives through delegated configuration and/or file-manager access. If only full device or fleet administrators can provide those archives, the issue is described as hardening rather than a crossed security boundary.

2

What configuration must be enabled for the vulnerable extraction path to be used?

The Docker Compose build context path must be enabled through UseContext. The issue occurs while qbee-agent unpacks the archive used for that build context.

3

What can an attacker write outside the intended directory?

A crafted sibling-prefix traversal archive entry can cause qbee-agent to create directories and regular files in nearby cache or project paths that share the destination prefix. The available information does not establish arbitrary absolute-path writes or direct code execution.

4

How can I determine whether a system is affected?

Systems running qbee-agent versions prior to 2026.41 are affected when UseContext is enabled and a delegated, less-privileged party can supply Docker Compose context archives. Systems where archive submission is restricted to full device or fleet administrators do not have the described privilege-boundary exposure.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203