CVE-2026-90648 wabt: RLBox: WasmBoxC: firefox: wasm2c: Sandbox escape via memory allocation failure
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: partial
- Technology
- UbuntuDebian
Description
wasm2c in WebAssembly wabt through 1.0.41 allows sandbox escape in some situations that primarily involve 32-bit platforms, aka a "table flip" attack. It does not check the return value of calloc() in wasm_rt_allocate_funcref_table() (wasm2c/wasm-rt-impl-tableops.inc). When the funcref table allocation fails, table->data is left NULL while table->size keeps the guest-declared element count; thus, bounds checks still pass and table element accesses resolve to absolute memory addresses (i * sizeof(wasm_rt_funcref_t)). This gives arbitrary read and write of host process memory and - via table.get, table.set, and call_indirect - arbitrary code execution, defeating the isolation that wasm2c exists to provide (a full sandbox escape). wasm2c is used as an in-process sandboxing boundary by RLBox and WasmBoxC, including in Firefox, which compiles the Graphite, Hunspell, Ogg, Expat, and Woff2 libraries via wasm2c to contain untrusted font, media, and XML input. Therefore, sandboxing in these applications is potentially affected. Exploitation requires the funcref table allocation to fail, for example under an address-space limit (RLIMIT_AS), on 32-bit hosts, with vm.overcommit_memory=2, or under memory pressure. On 64-bit Linux with default overcommit the allocation succeeds and the defect is not triggered. The wasm2c memory allocator aborts on calloc failure in the same runtime; the table allocator lacks this abort behavior. This was introduced in commit ab9e0b55 (PR #813).
Upgrade path
8 packages: 2 fixed, 6 with no fix yet.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| debian/wabt(Debian 12) | = 1.0.32-1; = 1.0.33-1; = 1.0.34+dsfg+~cs1.0.32-1; = 1.0.34+dsfg2+~cs1.0.32-1 +11 more | No fix listed | No fix yet |
| debian/wabt(Debian 13) | = 1.0.36+dfsg+~cs1.0.36-2; = 1.0.41+dfsg+~cs1.0.39-1; = 1.0.41+dfsg+~cs1.0.39-2; = 1.0.42+dfsg+~cs1.0.39-1 +2 more | No fix listed | No fix yet |
| ubuntu/wabt(Ubuntu 22.04) | All versions | No fix listed | No fix yet |
| ubuntu/wabt(Ubuntu 24.04) | All versions | No fix listed | No fix yet |
| ubuntu/wabt(Ubuntu 26.04) | All versions | No fix listed | No fix yet |
| ubuntu/wabt(Ubuntu 26.10) | All versions | No fix listed | No fix yet |
| debian/wabt(Debian 14) | < 1.0.42+dfsg+~cs1.0.39-2; = 1.0.36+dfsg+~cs1.0.36-2; = 1.0.41+dfsg+~cs1.0.39-1; = 1.0.41+dfsg+~cs1.0.39-2 +1 more | 1.0.42+dfsg+~cs1.0.39-2 | Fixed |
| webassembly wabt | <= 1.0.41 | after 1.0.41 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| webassembly wabt | <= 1.0.41 | No fix listed |
| debian/wabt(Debian:12) | All versions | No fix listed |
| debian/wabt(Debian:12) | = 1.0.32-1 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.33-1 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.34+dsfg+~cs1.0.32-1 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.34+dsfg2+~cs1.0.32-1 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.34+dsfg2+~cs1.0.32-2 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.34+dsfg2+~cs1.0.32-3 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.34+dsfg2+~cs1.0.32-4 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.34-1 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.36+dfsg+~cs1.0.36-1 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.36+dfsg+~cs1.0.36-2 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.41+dfsg+~cs1.0.39-1 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.41+dfsg+~cs1.0.39-2 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.42+dfsg+~cs1.0.39-1 | No fix listed |
| debian/wabt(Debian:12) | = 1.0.42+dfsg+~cs1.0.39-2 | No fix listed |
| debian/wabt(Debian:13) | All versions | No fix listed |
| debian/wabt(Debian:13) | = 1.0.36+dfsg+~cs1.0.36-2 | No fix listed |
| debian/wabt(Debian:13) | = 1.0.41+dfsg+~cs1.0.39-1 | No fix listed |
| debian/wabt(Debian:13) | = 1.0.41+dfsg+~cs1.0.39-2 | No fix listed |
| debian/wabt(Debian:13) | = 1.0.42+dfsg+~cs1.0.39-1 | No fix listed |
| debian/wabt(Debian:13) | = 1.0.42+dfsg+~cs1.0.39-2 | No fix listed |
| debian/wabt(Debian:14) | < 1.0.42+dfsg+~cs1.0.39-2 | 1.0.42+dfsg+~cs1.0.39-2 |
| debian/wabt(Debian:14) | = 1.0.36+dfsg+~cs1.0.36-2 | No fix listed |
| debian/wabt(Debian:14) | = 1.0.41+dfsg+~cs1.0.39-1 | No fix listed |
Show 6 more
| Product | Affected versions | Fixed in |
|---|---|---|
| debian/wabt(Debian:14) | = 1.0.41+dfsg+~cs1.0.39-2 | No fix listed |
| debian/wabt(Debian:14) | = 1.0.42+dfsg+~cs1.0.39-1 | No fix listed |
| ubuntu/wabt(Ubuntu:22.04) | All versions | No fix listed |
| ubuntu/wabt(Ubuntu:24.04) | All versions | No fix listed |
| ubuntu/wabt(Ubuntu:26.04) | All versions | No fix listed |
| ubuntu/wabt(Ubuntu:26.10) | All versions | No fix listed |
References
- github.com exploit technical-description
- github.com product
- bugzilla.mozilla.org related
- blog.mozilla.org related
- rlbox.dev related
- Red Hat CVE page vendor-advisory
- Red Hat Bugzilla 2532629 issue-tracking
- www.cve.org
- nvd.nist.gov
- Debian Security Tracker CVE-2026-90648 vendor-advisory
- Ubuntu CVE tracker vendor-advisory
- bugs.debian.org issue-tracking
- ENISA EUVD EUVD-2026-76923 third-party-advisory