dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-46703

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Boxlite versions before 0.9.0 fail to validate symlinks when processing tar entries in OCI images. Malicious images can contain symlinks pointing to absolute host paths, allowing attackers to write arbitrary files to the host filesystem and achieve remote code execution.

MitigationUpgrade to Boxlite version 0.9.0 or later which patches the symlink validation vulnerability. Avoid loading OCI images from untrusted sources until the upgrade is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Boxlite installation and version
    Run any available command to query the installed Boxlite version (such as 'boxlite --version', 'boxlite version', or check package manager listings)
    Affected if The installed version is below 0.9.0
  2. Confirm OCI image processing is in use
    Review logs, configurations, or command history to determine if Boxlite is being used to load or process OCI image tar files
    Affected if OCI image tar processing feature is actively being used with untrusted images
  3. Inspect symlink handling behavior
    Examine Boxlite configuration or code for settings controlling symlink resolution during tar extraction, or test by processing a benign OCI image with absolute symlinks
    Affected if The software resolves symlinks without validating target paths fall within the intended extraction directory

You are affected if Boxlite version is below 0.9.0 AND you process OCI image tar files, especially from untrusted sources, since the vulnerability allows arbitrary file write via malicious absolute-path symlinks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Boxlite version 0.9.0 or later which patches the symlink validation vulnerability. Avoid loading OCI images from untrusted sources until the upgrade is applied.

Recommended fix High confidence

0.9.0

  1. Identify the current installed version of Boxlite using package manager or project dependencies
  2. Upgrade Boxlite to version 0.9.0 or later using the appropriate package manager or installation method
  3. Verify the upgrade was successful by checking the installed version
  4. If using a package manager (e.g., pip, npm, cargo), run: pip install boxlite==0.9.0 (or equivalent for your package manager)
  5. If using Docker or OCI containers, pull the updated image tagged 0.9.0 or later
  6. Restart any services running Boxlite to ensure the patched version is loaded
  7. Review any custom OCI image configurations to ensure no longer using untrusted images

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46703 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46703 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data