dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-46695

CRITICAL · 10.0 CVSS v3.1 Published 2026-06-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 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 directories that should be read-only. 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 · moderate confidence

Boxlite before v0.9.0 fails to restrict kernel capabilities inside OCI containers, allowing malicious code to remount directories from read-only to read-write mode. This enables arbitrary write access to directories that should be protected, bypassing the sandbox's read-only isolation.

MitigationUpgrade Boxlite to version 0.9.0 or later, which contains the capability restriction patch. In the interim, ensure containers run with minimal capabilities and consider additional isolation layers.

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

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 version
    Run 'boxlite --version' or check the installed package version using your system's package manager (dpkg, rpm, or similar)
    Affected if Version is earlier than 0.9.0
  2. Review container runtime configuration
    Examine the Boxlite configuration file or container spec for the 'securityContext.capabilities.add' setting. For running containers, use 'boxlite inspect <container>' or 'docker inspect <container>' to view granted capabilities
    Affected if Containers are granted capabilities beyond the baseline (especially CAP_SYS_ADMIN, CAP_DAC_OVERRIDE, or CAP_MKNOD)
  3. Verify capability restrictions in container manifests
    Check container definition files (e.g., containerd shim config, Boxlite runtime config) for any security profiles or seccomp settings that limit capabilities
    Affected if No capability restrictions are defined, or the security profile explicitly allows mount operations
  4. Test mount capability availability
    From within a container, attempt to run 'mount -o remount,rw /' or check for CAP_SYS_ADMIN capability using 'capsh --print' if available inside the container
    Affected if The remount succeeds or CAP_SYS_ADMIN is listed in the container's effective capabilities

You are affected if Boxlite version is below 0.9.0 AND your containers run with excessive kernel capabilities (particularly CAP_SYS_ADMIN) that allow remounting read-only filesystems.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Boxlite to version 0.9.0 or later, which contains the capability restriction patch. In the interim, ensure containers run with minimal capabilities and consider additional isolation layers.

Recommended fix High confidence

Boxlite version 0.9.0

  1. Identify the current version of Boxlite being used (e.g., check via `boxlite --version` or package manager)
  2. Stop the Boxlite service if running
  3. Upgrade Boxlite to version 0.9.0 or later using the appropriate package manager or installation method
  4. Verify the upgrade was successful by checking the version
  5. Restart the Boxlite service

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46695 — 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-46695 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