CVE-2025-6272 json
wasm3 m3_compile.c MarkSlotAllocated out-of-bounds write
published 2025-06-19 16 mo ago modified 2026-06-17 4 mo ago also GHSA-rrmw-gv85-w824 , PYSEC-2025-186 , EUVD-2025-18691
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
A vulnerability has been found in wasm3 0.5.0 and classified as problematic. This vulnerability affects the function MarkSlotAllocated of the file source/m3_compile.c. The manipulation leads to out-of-bounds write. An attack has to be approached locally. The exploit has been disclosed to the public and may be used.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 16 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/wasm3/wasm3/issues/531 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/user-attachments/files/19516600/wasm3_crash.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:X/RC:R |
| CNA | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:X/RC:R |
| CNA | 2.0 | 1.7 | AV:L/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:ND/RC:UR |
| CNA | 4.0 | 1.9 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| CNA | 2.0 | 1.7 | AV:L/AC:L/Au:S/C:N/I:N/A:P |
| GitHub | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pywasm3 | <=0.5.0 |
no fix listed |
Affected products
- n/a wasm3
Classification
References
-
github.com
/wasm3/wasm3/issues/531
issue-tracking, exploit, web, report
-
github.com
/user-attachments/files/19516600/wasm3_crash.txt
exploit, web, evidence
-
vuldb.com
/?id.313276
vdb-entry, technical-description, web, third-party-advisory, advisory
-
vuldb.com
/?ctiid.313276
signature, permissions-required, web, third-party-advisory, vdb-entry, report
-
vuldb.com
/?submit.593008
third-party-advisory, web, vdb-entry, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-6272
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/pywasm3/PYSEC-2025-186.yaml
web
-
github.com
/wasm3/pywasm3
package
-
github.com
/wasm3/pywasm3/blob/main/wasm3/m3_compile.c#L333
web
-
github.com
/advisories/GHSA-rrmw-gv85-w824
advisory
Sources
- CVE List CVE-2025-6272
- GitHub Advisory GHSA-rrmw-gv85-w824
- NVD CVE-2025-6272
- OSV PYSEC-2025-186
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.