VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

wasm3: vulnerability history, versions and safety

wasm3 is a package in the OSS-Fuzz ecosystem. Vulert records 16 vulnerabilities for it across 1 release, from Apr 2021 to Sep 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
16 vulnerabilities recorded H10 M4 U2
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all wasm3 vulnerabilities

Vulert verdict on wasm3 i

Updated on 23 Oct 2026

Careful: 3 of the 16 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 16 vulnerabilities on record across 1 year, none in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 16 over 1 year · 0 in the last year i
  • Latest disclosure 11 Sep 2022 i
  • Highest CVSS n/a i
  • With no published fix 3 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for wasm3, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
v0.5.0 H4 M2 U1 No Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 14
  • 2022 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 16 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for wasm3

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-use-after-free vulnerability in wasm3 N/A medium No fix published 11 Sep 2022
Heap-buffer-overflow in op_Const64 in wasm3 N/A high b48695bb940e55c0baa0a3d5740cf48e03643b58 17 Apr 2021
Vulnerability in wasm3: UNKNOWN READ in op_BranchIfPrologue_s N/A high 12a5277ec0977af493530b704a5a16e28f734788 20 Apr 2021
Heap-buffer-overflow in op_Const64 in wasm3 N/A high 321ba58316e77b5f4d977897aaa4bdbe43a5e38b 23 Apr 2021
UNKNOWN WRITE vulnerability in wasm3 N/A high 321ba58316e77b5f4d977897aaa4bdbe43a5e38b 23 Apr 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About wasm3

Is wasm3 safe to use?

Vulert records 16 vulnerabilities for wasm3 in OSS-Fuzz: 0 critical, 10 high, 4 medium and 0 low, plus 2 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does wasm3 have?

16 vulnerabilities are recorded for wasm3 in the OSS-Fuzz ecosystem: 0 critical, 10 high, 4 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new wasm3 vulnerabilities disclosed?

0 vulnerabilities were recorded for wasm3 in the last 12 months, and the oldest entry in this database dates to 17 Apr 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of wasm3 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor wasm3 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the wasm3 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.