Low severity · published Jun 19, 2025
CVE-2025-6273
WebAssembly wabt binary-reader-objdump.cc LogOpcode assertion
3.3
CVSS
0.2%
EPSS
No
On KEV
Description
A vulnerability was found in WebAssembly wabt up to 1.0.37 and classified as problematic. This issue affects the function LogOpcode of the file src/binary-reader-objdump.cc. The manipulation leads to reachable assertion. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The code maintainer explains that this issue might not affect "real world wasm programs".
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
None
Integrity
None
Availability
Low
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 14% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
WA
wabt · WebAssembly
1.0.0; 1.0.1; 1.0.2; 1.0.3; 1.0.4; 1.0.5; +32 more · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-6273
CVE.org
https://www.cve.org/CVERecord?id=CVE-2025-6273
Exploit
https://github.com/WebAssembly/wabt/issues/2574
Exploit
https://github.com/user-attachments/files/19529411/wabt_crash.txt
Permissions Required
https://vuldb.com/?ctiid.313277
Third Party Advisory
https://vuldb.com/?id.313277
Third Party Advisory
https://vuldb.com/?submit.593010
More from wabt
8.8
CVE-2025-2368
WebAssembly wabt Malformed File binary-reader-interp.cc OnExport heap-based overflow
7.8
CVE-2025-15412
WebAssembly wabt wasm-decompile VarName out-of-bounds
7.8
CVE-2025-15411
WebAssembly wabt wasm-decompile InsertNode memory corruption
7.1
CVE-2026-90648
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
7.1
CVE-2022-43280
wasm-interp v1.0.29 was discovered to contain an out-of-bounds read via the component OnReturnCallExpr->GetReturnCallDropKeepCount