CVE-2025-69261: WasmEdge is a WebAssembly runtime

Q: How do I fix CVE-2025-69261?

wasmedge: upgrade to 0.16.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-69261 being exploited?

CVE-2025-69261 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-69261 affect?

CVE-2025-69261 affects wasmedge. Severity is high (CVSS 7.5). WasmEdge is a WebAssembly runtime. Prior to version 0.16.0-alpha.3, a multiplication in `WasmEdge/include/runtime/instance/memory.h` can wrap, causing `checkAccessBound()` to incorrectly allow the access. This leads to a segmentation fault.

Q: How urgent is CVE-2025-69261?

Priority 43/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

This month

HIGH 7.5REMOTEWATCHLISTUPGRADE

CVE-2025-69261 is a high-severity flaw (CVSS 7.5) affecting wasmedge. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

WasmEdge is a WebAssembly runtime. Prior to version 0.16.0-alpha.3, a multiplication in `WasmEdge/include/runtime/instance/memory.h` can wrap, causing `checkAccessBound()` to incorrectly allow the access. This leads to a segmentation fault. Version 0.16.0-alpha.3 contains a patch for the issue.

Why this priority

High severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-190
Published	2025-12-30
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: linuxfoundation

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-12-30 20:16 UTCPublished CVE record published
2026-06-17 10:00 UTCUpdated Record last modified

linuxfoundation wasmedge UPGRADE

Affected: < 0.16.0 · 0.16.0 alpha1 · 0.16.0 alpha2

Fixed in: 0.16.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wasmedge || rpm -q wasmedge || wasmedge --version

2. UPGRADE to 0.16.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wasmedge

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wasmedge

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-2025-69261?

wasmedge: upgrade to 0.16.0. Exact commands for each OS are on this page.

Is CVE-2025-69261 being exploited?

CVE-2025-69261 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-2025-69261 affect?

CVE-2025-69261 affects wasmedge. Severity is high (CVSS 7.5). WasmEdge is a WebAssembly runtime. Prior to version 0.16.0-alpha.3, a multiplication in `WasmEdge/include/runtime/instance/memory.h` can wrap, causing `checkAccessBound()` to incorrectly allow the access. This leads to a segmentation fault.

How urgent is CVE-2025-69261?

Priority 43/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

References

← Back to latest CVEs