Vulnerability · CVE-2026-55107
kobako Sandbox Escape: guest eval reaches host RCE via method_missing → public_send (any bound Service)
Published Aug 18, 2026 · catalog updated Oct 26, 2026 · kobako Sandbox Escape: guest
Last checked Oct 31, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-55107. EPSS is 0.80%. Act only if a listed version of kobako Sandbox Escape: guest is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (kobako Sandbox Escape: guest).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Critical10.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.80%
- Remediation
- Advisory link
- Affected products
- RubyGems kobako
### Summary A guest mruby script running inside the Kobako sandbox can execute arbitrary Ruby in the host process, fully escaping the sandbox. ### Details A host embeds bound "Service" objects that guest scripts call across the wasm boundary through the transport dispatcher. The dispatcher passed the guest-supplied method name straight to on the bound object, with no restriction to the object's own methods: can invoke any public method, including Ruby's ambient reflection surface. A guest pivots through the public into otherwise private Kernel methods: a dispatch request with and evaluates to , running attacker-controlled Ruby in the host. Any bound Service object is sufficient — no Service-specific behavior is required. ### Proof of Concept A guest call equivalent to: executes in the host process and can read or modify host state, spawn processes, and so on. ### Impact Complete sandbox escape leading to remote code execution in the host process, defeating the gem's central guarantee of isolating untrusted mruby scripts. Any deployment that runs untrusted or attacker-influenced scripts is affected. All released versions (0.1.0 through 0.9.0) are vulnerable; the dispatcher carried the same unguarded sink under three successive names ( → → ). ### Patches Fixed in 0.9.1. The dispatcher now rejects any method whose resolved owner is a core/meta module ( , , , , ), so only methods the bound object itself defines — or dynamically handles via — remain reachable. The ambient reflection methods ( , , , , , , , …) are all owned by those modules and are blocked. ### Workarounds None within the affected versions. Until you can upgrade, do not bind any host Service object into a sandbox that runs untrusted scripts. Upgrade to 0.9.1. ### References - GHSA-7pwq-q9jf-539h - Fix commit: 64f8470 ### Credits Reported and fixed by Ahmed Al Hafoudh.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- RubyGems kobako0.1.0 → 0.9.1
How to fix CVE-2026-55107
Upgrade
CVE-2026-55107 lists a fix boundary at 0.9.1. Compare the installed build with that boundary before you change production.
Version check
Seen in 0.1.0 → 0.9.1
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-55107. EPSS is 0.80%. Act only if a listed version of kobako Sandbox Escape: guest is installed.
Which versions are affected?
Compare what you have installed with 0.1.0 → 0.9.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-470; CWE-94: Code Injection. EPSS 0.80%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Aug 18, 2026 · GitHub Advisory Database
Detected
### Summary A guest mruby script running inside the Kobako sandbox can execute arbitrary Ruby in the host process, fully escaping the sandbox. ### Details A host embeds bound "Service" objects that guest scripts call across the wasm boundary through the transport dispatcher. The dispatcher passed the guest-supplied method name straight to on the bound object, with no restriction to the object's ow
Oct 26, 2026 · GitHub Advisory Database
Fix available
kobako fixed in 0.9.1
Oct 26, 2026 · GitHub Advisory Database
Fix available
kobako fixed in 0.9.1
Oct 26, 2026 · GitHub Advisory Database
Updated
### Summary A guest mruby script running inside the Kobako sandbox can execute arbitrary Ruby in the host process, fully escaping the sandbox. ### Details A host embeds bound "Service" objects that guest scripts call across the wasm boundary through the transport dispatcher. The dispatcher passed the guest-supplied method name straight to on the bound object, with no restriction to the object's ow
Sources
- CVE.orgVulnerability recordCVE-2026-55107
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-7pwq-q9jf-539h
GitHub Advisory Database record mirrored by OSV.
github.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-7pwq-q9jf-539h
kobako Sandbox Escape: guest eval reaches host RCE via method_missing → public_send (any bound Service)
osv.dev
References
Freshness
Last verified in this catalog Oct 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- GitHub Advisory DatabaseOct 31, 2026
- OpenSSF OSV / OSV ScannerOct 31, 2026
- CVE.orgOct 27, 2026