Quick answers
- Is CVE-2026-47213 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47213 being exploited in the wild.
- How severe is CVE-2026-47213?
- Medium severity, with a CVSS score of 6.5, published 10 June 2026.
- Which products and versions are affected?
- boxlite (PyPI) <= 0.8.2, ECOSYSTEM:introduced=0,last_affected=0.8.2.
- Is there a fix for CVE-2026-47213?
- A patch was published on 2026-05-19: Fix committed to repository and advisory published by vendor. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47213 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-47213?
- Check whether you run boxlite (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Boxlite versions 0.8.2 and prior contain a resource management vulnerability in the timeout watcher component (`src/guest/src/service/exec/timeout.rs`). When a user-configured execution timeout is reached, the service incorrectly issues a `SIGALRM` (signal 14) instead of a `SIGKILL` (signal 9). Because `SIGALRM` can be caught or ignored by the guest process (e.g., via `signal.SIG_IGN` in Python or `trap` in shell), malicious code can bypass the timeout and continue running. This leads to improper resource shutdown (CWE-404) and can result in denial-of-service through resource exhaustion. The issue has been patched in commit 28159fc by implementing a two-stage termination process (SIGTERM followed by a SIGKILL fallback).
Affected products
- boxlite-ai Boxlite <= 0.8.2
Identifiers
- CVE-2026-47213
- GHSA-xjhv-pp2r-6f82
- PYSEC-2026-2400
Timeline
- 2026-05-19: patched: Fix committed to repository and advisory published by vendor.
- 2026-06-10: disclosed: CVE published to NVD.