CVE-2023-46332: WebAssembly wabt 1.0.33 contains an Out-of-Bound Memory Write in DataSegment::Drop(), which lead to segmentati
CVE-2023-46332 is a medium-severity flaw (CVSS 5.5) affecting webassembly binary toolkit. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
WebAssembly wabt 1.0.33 contains an Out-of-Bound Memory Write in DataSegment::Drop(), which lead to segmentation fault.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 5.5 (Medium) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.3% (top 78%) |
| CISA exploited list | No |
| Weakness | CWE-787 |
| Published | 2023-10-23 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-46332?
webassembly binary toolkit: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2023-46332 being exploited?
CVE-2023-46332 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-46332 affect?
CVE-2023-46332 affects webassembly binary toolkit. Severity is medium (CVSS 5.5). WebAssembly wabt 1.0.33 contains an Out-of-Bound Memory Write in DataSegment::Drop(), which lead to segmentation fault.
How urgent is CVE-2023-46332?
Priority 30/100. Public exploit reference
Related CVEs
- CVE-2025-3122 LOW 3.1 DOWNGRADE A vulnerability classified as problematic was found in WebAssembly wabt 1.0.36
- CVE-2023-46331 MEDIUM 5.5 DOWNGRADE WebAssembly wabt 1.0.33 has an Out-of-Bound Memory Read in in DataSegment::IsValidRange(), which lead to segme