BoxLite has a Timeout Bypass Vulnerability
CVE-2026-47213GHSA-xjhv-pp2r-6f82
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
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.
Affected packages
PyPI boxlite
- Affected
- <= 0.8.2
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-xjhv-pp2r-6f82 lists affected ranges: PyPI boxlite >=0 <=0.8.2
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xjhv-pp2r-6f82 lists affected ranges: PyPI boxlite >=0 <=0.8.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- CVE-2026-47213: 0.27% estimated exploitation activity in the next 30 days; percentile 19.06 (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 run OCI containers within them. BoxLite allows users to configure a timeout for services running inside the virtual machine. When the timeout is triggered, BoxLite sends a signal to kill the process. However, instead of using the uncatchable SIGKILL signal, BoxLite uses the catchable SIGALRM signal. Malicious code running inside the sandbox can exploit this vulnerability to continue running after the timeout is triggered, leading to resource exhaustion within the virtual machine and affecting the availability of the BoxLite service. Details 1. ExecRequest with timeoutms arrives at Execution service File: guest/src/service/exec/mod.rs Function: spawnexecution() (line 315) Code: Issue: Any nonzero timeoutms triggers the timeout watcher. The host expects this to kill the process after the specified duration. 2. Timeout watcher sends SIGALRM instead of SIGKILL File:…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-xjhv-pp2r-6f82
- Revision 1 · created ·
Published from osv record GHSA-xjhv-pp2r-6f82
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-47213 Advisory: BoxLite has a Timeout Bypass Vulnerability IDs: CVE-2026-47213, GHSA-xjhv-pp2r-6f82 Record: https://patchnext.com/advisories/cve-2026-47213 (revision 2, source checked 26 Oct 2026, 13:45 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI boxlite: affected <= 0.8.2 ## Suggested inspection (read-only) - `python -m pip show boxlite`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on boxlite. - 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://osv.dev/vulnerability/GHSA-xjhv-pp2r-6f82 (OSV record GHSA-xjhv-pp2r-6f82 lists affected ranges: PyPI boxlite >=0 <=0.8.2) - Verified: https://github.com/advisories/GHSA-xjhv-pp2r-6f82 (GitHub-reviewed advisory GHSA-xjhv-pp2r-6f82 lists affected ranges: PyPI boxlite >=0 <=0.8.2) Commands are suggestions: review each one before running it.
Loading voting…