# CVE-2026-46703: BoxLite: Path Traversal Vulnerability in boxlite Leads to Arbitrary File Write on the Host > Attackers can write arbitrary files to the host via malicious OCI images, potentially leading to remote code execution. - **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 10 Jun 2026 - **Updated:** 11 Jun 2026 - **Also known as:** GHSA-f396-4rp4-7v2j, GO-2026-5344, PYSEC-2026-298, RUSTSEC-2026-0148 ## What is CVE-2026-46703? CVE-2026-46703 is a critical path traversal vulnerability in boxlite-ai boxlite, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Boxlite is a sandbox service that allows users to create lightweight virtual machines (Boxes) and launch OCI containers within them to run untrusted code. Prior to version 0.9.0, Boxlite allows users to specify the OCI image used by containers in the sandbox. However, when processing tar entries in OCI images, Boxlite does not account for the possibility that entries may be symlinks pointing to absolute paths. An attacker can craft a malicious OCI image and distribute it on image hosting platforms such as DockerHub, tricking users into using it. Once a user loads the malicious image, the attacker can write arbitrary content to any path on the host, which can further lead to remote code execution on the host. This issue has been patched in version 0.9.0. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-46703? 13 open source packages ship an affected version, including github.com/boxlite-ai/boxlite/sdks/go, boxlite and boxlite-cli. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/boxlite-ai/boxlite/sdks/go` | Go | All versions | 0.9.0 | | `github.com/boxlite-ai/boxlite/sdks/go` | Go | All versions | 0.9.0 | | `github.com/boxlite-ai/boxlite/sdks/go` | Go | All versions | 0.9.0 | | `boxlite` | PyPI | All versions | 0.9.0 | | `boxlite` | PyPI | All versions | 0.9.0 | | `boxlite` | PyPI | All versions | 0.9.0 | | `boxlite` | crates.io | All versions | 0.9.0 | | `boxlite` | crates.io | All versions | 0.9.0 | | `boxlite` | crates.io | From 0.0.0-0 | 0.9.0 | | `boxlite-cli` | crates.io | All versions | 0.9.0 | | `boxlite-cli` | crates.io | All versions | 0.9.0 | | `@boxlite-ai/boxlite` | npm | All versions | 0.9.0 | | `@boxlite-ai/boxlite` | npm | All versions | 0.9.0 | ## How do I fix CVE-2026-46703? Upgrade github.com/boxlite-ai/boxlite/sdks/go to 0.9.0 or later. ## Is CVE-2026-46703 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46703 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-46703 and fix it if it is affected. What it is: CVE-2026-46703 is a critical path traversal vulnerability in boxlite-ai boxlite, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46703 exists. Affected packages and fixed versions: - github.com/boxlite-ai/boxlite/sdks/go (Go): affected all versions; fixed in 0.9.0 - github.com/boxlite-ai/boxlite/sdks/go (Go): affected all versions; fixed in 0.9.0 - github.com/boxlite-ai/boxlite/sdks/go (Go): affected all versions; fixed in 0.9.0 - boxlite (PyPI): affected all versions; fixed in 0.9.0 - boxlite (PyPI): affected all versions; fixed in 0.9.0 - boxlite (PyPI): affected all versions; fixed in 0.9.0 - boxlite (crates.io): affected all versions; fixed in 0.9.0 - boxlite (crates.io): affected all versions; fixed in 0.9.0 - boxlite (crates.io): affected from 0.0.0-0; fixed in 0.9.0 - boxlite-cli (crates.io): affected all versions; fixed in 0.9.0 - boxlite-cli (crates.io): affected all versions; fixed in 0.9.0 - @boxlite-ai/boxlite (npm): affected all versions; fixed in 0.9.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-46703/ (Markdown: https://insights.sbomify.com/CVE-2026-46703/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46703 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46703 - OSV: https://osv.dev/vulnerability/CVE-2026-46703 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-46703/ Summaries are generated and may contain mistakes; the official description above is the record.