CVE-2026-129237 json
qbee-agent: Docker Compose build context Zip Slip writes outside context directory
published last mo. modified yesterday also EUVD-2026-126529 , GHSA-vx32-xf7g-9ghr
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go go.qbee.io/agent 0.0.0-20260908095235-eb7875f0a849
- github.com/qbee-io/qbee-agent@eb7875f commit
- github.com/qbee-io/qbee-agent#148 pull request
- github.com/qbee-io/qbee-agent/releases/tag/2026.41 release
Is CVE-2026-129237 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | go.qbee.io/agent | <0.0.0-20260908095235-eb7875f0a849 |
0.0.0-20260908095235-eb7875f0a849 |
Affected products
- qbee-io qbee-agent
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/qbee-io/qbee-agent/pull/148
web
-
github.com
/qbee-io/qbee-agent/commit/eb7875f0a849cb33325956d0b75e27061d7a7fa3
web
-
github.com
/qbee-io/qbee-agent/security/advisories/GHSA-vx32-xf7g-9ghr
web, advisory
-
github.com
/qbee-io/qbee-agent/releases/tag/2026.41
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-129237
advisory
-
github.com
/qbee-io/qbee-agent
package
Sources
- CVE List CVE-2026-129237
- GitHub Advisory GHSA-vx32-xf7g-9ghr
- NVD CVE-2026-129237
- Maintainer advisory GHSA-vx32-xf7g-9ghr
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of qbee-io/qbee-agent published their own advisory on GitHub. Reviewed sources take precedence over it.