Skip to content

[GHSA-vvp9-h8p2-xwfc] Wasmtime: Memory leak in C API with externref and anyref types#8784

Open
HsiangNianian wants to merge 1 commit into
github:HsiangNianian/advisory-improvement-8784from
HsiangNianian:HsiangNianian-GHSA-vvp9-h8p2-xwfc
Open

[GHSA-vvp9-h8p2-xwfc] Wasmtime: Memory leak in C API with externref and anyref types#8784
HsiangNianian wants to merge 1 commit into
github:HsiangNianian/advisory-improvement-8784from
HsiangNianian:HsiangNianian-GHSA-vvp9-h8p2-xwfc

Conversation

@HsiangNianian

Copy link
Copy Markdown

Problem

GHSA-vvp9-h8p2-xwfc states that the regression was introduced in Wasmtime 37.0.0 and that 36.0.x and all prior versions are unaffected. The Rust package range starts at 37.0.0, but the PyPI wasmtime-bin range starts at 0. Because PyPI publishes wasmtime-bin 36.0.9, the current range marks an explicitly unaffected release as vulnerable.

Change

  • Start the PyPI wasmtime-bin affected range at 37.0.0.
  • Keep the 37.0.2 fixed boundary, Rust package range, and all other advisory metadata unchanged.

Evidence

Validation

  • python3 -m json.tool advisories/github-reviewed/2026/07/GHSA-vvp9-h8p2-xwfc/GHSA-vvp9-h8p2-xwfc.json
  • jq -e '[.affected[] | select(.package.name == "wasmtime-bin") | .ranges[0].events[0].introduced, .ranges[0].events[1].fixed] == ["37.0.0", "37.0.2"]' advisories/github-reviewed/2026/07/GHSA-vvp9-h8p2-xwfc/GHSA-vvp9-h8p2-xwfc.json
  • git diff --check upstream/main...HEAD

The advisory states that the regression was introduced in 37.0.0 and that prior releases are unaffected. Align the PyPI range with the existing Rust range so wasmtime-bin 36.x is not flagged.
@github-actions
github-actions Bot changed the base branch from main to HsiangNianian/advisory-improvement-8784 July 23, 2026 05:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant