CVE-2026-129237
Last modified
CVE-2026-129237 is a medium-severity vulnerability rated 5.4/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| qbee-io | qbee-agent | < 2026.41 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-129237?
How severe is CVE-2026-129237?
How do I fix CVE-2026-129237?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-12920The Cookie Banner for GDPR / CCPA – WPLP Cookie Consent plug…4.9
- CVE-2026-12921In AzeoTech DAQFactory versions 21.1 and prior, a Use After …7.8
- CVE-2026-129217In FRRouting (FRR) 8.3 through 10.5.1, bgp_notify_decapsulat…6
- CVE-2026-12923The Youtube Showcase plugin for WordPress is vulnerable to A…7.5
- CVE-2026-129235Kubeshark is an eBPF-powered network observability tool for …5.3
- CVE-2026-129236Kubeshark is an eBPF-powered network observability tool for …7.2
- CVE-2026-129239Directus is a real-time API and App dashboard for managing S…6.5
- CVE-2026-12924The Eventin – Event Calendar, Event Registration, Tickets & …6.4
- CVE-2026-129247A security flaw has been discovered in yangzongzhuan RuoYi u…4.7
- CVE-2026-129248A weakness has been identified in Akaunting up to 3.3.0. The…4.3
- CVE-2026-129250A security vulnerability has been detected in Edimax BR6478A…9.9
- CVE-2026-129251A vulnerability was detected in hrshadhin CloudSchool up to …2.4
Are you affected by CVE-2026-129237?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
