Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-90648

Quick assessment

Affected
WebAssembly wabt
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

WebAssembly WABT是WebAssembly组织开源的一个 WebAssembly 二进制工具包。 WebAssembly WABT 1.0.41及之前版本存在异常处理不当漏洞,该漏洞源于未检查wasm_rt_allocate_funcref_table()中calloc()的返回值,当funcref表分配失败时table->data为NULL而table->size仍保留元素数量,导致边界检查通过并可任意读写宿主进程内存,通过table.get、table.set和call_indirect

CVSS 7.1 · High EPSS 0.19% · P8

Affected Version Matrix 1

VendorProduct Version RangeStatus
WebAssembly wabt ≤ 1.0.41 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-90648

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: CVE Program / CVE List V5
Vulnerability 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).
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H
Source: CVE Program / CVE List V5
Vulnerability Type
未加检查的返回值
Source: CVE Program / CVE List V5
Vulnerability Title
WebAssembly WABT 异常处理不当漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
WebAssembly WABT是WebAssembly组织开源的一个 WebAssembly 二进制工具包。 WebAssembly WABT 1.0.41及之前版本存在异常处理不当漏洞,该漏洞源于未检查wasm_rt_allocate_funcref_table()中calloc()的返回值,当funcref表分配失败时table->data为NULL而table->size仍保留元素数量,导致边界检查通过并可任意读写宿主进程内存,通过table.get、table.set和call_indirect
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
WebAssembly wabt 0 ~ 1.0.41 -

II. Public POCs for CVE-2026-90648

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-90648

请登录查看更多情报信息。

Proof of Concept for CVE-2026-90648 (1)

Vendor Pages for CVE-2026-90648 (1)

Other References for CVE-2026-90648 (1)

IV. Related Vulnerabilities

V. Comments for CVE-2026-90648

No comments yet


Leave a comment