Vulnerability Database · OSS-Fuzz · Package report

wamr: vulnerability history, versions and safety

wamr is a package in the OSS-Fuzz ecosystem. Vulert records 3 vulnerabilities for it across 3 affected ranges, from Mar 2025 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 01 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on wamr i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 01 Feb 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 3 vulnerabilities on record across 1 year, 2 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 3 over 1 year · 2 in the last year i
  • Latest disclosure 01 Feb 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from efa8019bdba89de121f14d84484cecbf023df879 up to 9aaf3599ec69469f6ab3b4373bfb0d8e6b3345b9 (exclusive) 1
from 9a23968fdacc0df4ec7066bc19a412f8b7a8bd69 up to 9d1dc3e4d26fb50657bc5161d4aa5e2d06f7657d (exclusive) 1
from 9a23968fdacc0df4ec7066bc19a412f8b7a8bd69 up to 8d069c230c3cc83c622c4d338d84475ff15e3a00 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for wamr

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap Buffer Overflow Vulnerability in WAMR Package N/A high 9aaf3599ec69469f6ab3b4373bfb0d8e6b3345b9 22 Mar 2025
Critical Null-Dereference Vulnerability in WAMR Package N/A unrated 9d1dc3e4d26fb50657bc5161d4aa5e2d06f7657d 27 Jan 2026
Null-Dereference READ Vulnerability in WAMR Package N/A unrated 8d069c230c3cc83c622c4d338d84475ff15e3a00 01 Feb 2026

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 wamr

Is wamr safe to use?

Vulert records 3 vulnerabilities for wamr in OSS-Fuzz: 0 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does wamr have?

3 vulnerabilities are recorded for wamr in the OSS-Fuzz ecosystem: 0 critical, 1 high, 0 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 wamr vulnerabilities disclosed?

2 vulnerabilities were recorded for wamr in the last 12 months, and the oldest entry in this database dates to 22 Mar 2025. 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 wamr 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 wamr for upcoming vulnerabilities?

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