Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 10.0amended

BoxLite: Permission Bypass Allows Modification of Read-Only Files

CVE-2026-46695GHSA-g6ww-w5j2-r7x3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (boxlite 0.9.0; boxlite 0.9.0; boxlite-cli 0.9.0; @boxlite-ai/boxlite 0.9.0; github.com/boxlite-ai/boxlite/sdks/go 0.9.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-46695: 0.29% estimated exploitation activity in the next 30 days; percentile 21.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Boxlite is a sandbox service that allows users to create lightweight virtual machines (Boxes) and launch OCI containers within them to run untrusted code. One of the core security features claimed by Boxlite is the ability to mount host directories in read-only mode (readonly=True) into the VM via the virtiofs protocol (a host-guest shared filesystem protocol designed specifically for virtual machines), so that untrusted code can only read but not modify host data. Since the underlying function of the lightweight VM library libkrun used by Boxlite does not support mounting in read-only mode, Boxlite chooses to implement read-only by adding the MSRDONLY flag when mounting the directory after the VM starts. However, because Boxlite does not restrict the kernel capabilities available inside the container, malicious code can remount the directory in rw mode, thereby gaining write access to that directory. This allows malicious code to perform arbitrary write operations on…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-g6ww-w5j2-r7x3

  2. Revision 2 · amended ·

    Amended from osv record GHSA-g6ww-w5j2-r7x3

  3. Revision 1 · created ·

    Published from ghsa record GHSA-g6ww-w5j2-r7x3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46695

Advisory: BoxLite: Permission Bypass Allows Modification of Read-Only Files
IDs: CVE-2026-46695, GHSA-g6ww-w5j2-r7x3
Record: https://patchnext.com/advisories/cve-2026-46695 (revision 3, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: boxlite 0.9.0; boxlite 0.9.0; boxlite-cli 0.9.0; @boxlite-ai/boxlite 0.9.0; github.com/boxlite-ai/boxlite/sdks/go 0.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io boxlite: affected < 0.9.0; fixed in 0.9.0
- PyPI boxlite: affected < 0.9.0; fixed in 0.9.0
- crates.io boxlite-cli: affected < 0.9.0; fixed in 0.9.0
- npm @boxlite-ai/boxlite: affected < 0.9.0; fixed in 0.9.0
- Go github.com/boxlite-ai/boxlite/sdks/go: affected < 0.9.0; fixed in 0.9.0

## Suggested inspection (read-only)
- crates.io boxlite: check the installed version with your package manager.
- `python -m pip show boxlite`: prints the installed version. Run with the environment that serves production active.
- crates.io boxlite-cli: check the installed version with your package manager.
- `npm ls @boxlite-ai/boxlite --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- Go github.com/boxlite-ai/boxlite/sdks/go: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on boxlite, boxlite-cli, @boxlite-ai/boxlite, github.com/boxlite-ai/boxlite/sdks/go.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g6ww-w5j2-r7x3 (GitHub-reviewed advisory GHSA-g6ww-w5j2-r7x3 lists affected ranges: PyPI boxlite >=0 =0 <0.9.0)
- Verified: https://osv.dev/vulnerability/GHSA-g6ww-w5j2-r7x3 (OSV record GHSA-g6ww-w5j2-r7x3 lists affected ranges: PyPI boxlite >=0 =0 =0 =0 =0 <0.9.0 (fixed))
- Verified: https://github.com/advisories/GHSA-g6ww-w5j2-r7x3 (GitHub-reviewed advisory GHSA-g6ww-w5j2-r7x3 lists affected ranges: PyPI boxlite >=0 =0 =0 =0 =0 <0.9.0)

Commands are suggestions: review each one before running it.

Loading voting…