{"items":[{"id":"NVI-00012905","kind":"vulnerability","title":"Wasmtime: Preemption and traps during bulk operations enable breaking internal VM state","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-2hw9-mc66-jc2q","CVE-2026-104855"],"plain_summary":"GitHub lists this reviewed advisory for wasmtime, wasmtime. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-21782dd88adbcdfed582b753c2188e0c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-06T17:17:16.000Z","value":"2 LOW (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-2a1ba68d2f65661990ce1f36bdbcb291"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.276%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.20086. Missing scores are unknown.","source_id":"sr-21782dd88adbcdfed582b753c2188e0c"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0355cc9258f53060e442f9a38635174c","url":"https://github.com/advisories/GHSA-2hw9-mc66-jc2q","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2hw9-mc66-jc2q","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T01:40:00.567Z"},{"id":"sr-2a1ba68d2f65661990ce1f36bdbcb291","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-104855","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-104855","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:14.367Z"},{"id":"sr-21782dd88adbcdfed582b753c2188e0c","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-104855","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.263Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0355cc9258f53060e442f9a38635174c"],"technology":"wasmtime","known_exclusions":[],"conditions_summary":"### Impact\n\nWasmtime's implementation of bulk-data-transfer WebAssembly instructions, such as `memory.copy`, contains a vulnerability when a preemption via epochs or fuel is combined with altering the store's state or cancelling a computation. To prevent these operations from taking too long Wasmtime injects fuel/epoch checks during these operations, but this enables embedders, and possible WebAssembly, to witness intermediate state in the middle of the operation. Examples of this include:\n\n* When a non-nullable WebAssembly table is grown the new elements initially start as null and are filled in as part of a loop with preemption checks. If this computation is then cancelled this left the table in a grown-but-uninitialized state where subsequent usage via WebAssembly could possibly segfault. Loads from this table are assumed to not be null due to its type, but the runtime implementation was exposed through this cancellation at a preemption point.\n* Embedders could mutate the store during an epoch callback, such as growing a WebAssembly linear memory. During a bulk `memory.copy` operation, however, the pointers being copied to/from weren't recomputed between preemption points. This ","public_affected_ranges":[">= 46.0.0, < 46.0.2"]},{"certainty":"source_listed","source_ids":["sr-0355cc9258f53060e442f9a38635174c"],"technology":"wasmtime","known_exclusions":[],"conditions_summary":"### Impact\n\nWasmtime's implementation of bulk-data-transfer WebAssembly instructions, such as `memory.copy`, contains a vulnerability when a preemption via epochs or fuel is combined with altering the store's state or cancelling a computation. To prevent these operations from taking too long Wasmtime injects fuel/epoch checks during these operations, but this enables embedders, and possible WebAssembly, to witness intermediate state in the middle of the operation. Examples of this include:\n\n* When a non-nullable WebAssembly table is grown the new elements initially start as null and are filled in as part of a loop with preemption checks. If this computation is then cancelled this left the table in a grown-but-uninitialized state where subsequent usage via WebAssembly could possibly segfault. Loads from this table are assumed to not be null due to its type, but the runtime implementation was exposed through this cancellation at a preemption point.\n* Embedders could mutate the store during an epoch callback, such as growing a WebAssembly linear memory. During a bulk `memory.copy` operation, however, the pointers being copied to/from weren't recomputed between preemption points. This ","public_affected_ranges":[">= 47.0.0, < 47.0.3"]}],"null_published_at":"2026-11-04T18:04:03.158Z","source_updated_at":"2026-10-02T22:45:30.000Z","source_disclosed_at":"2026-10-02T22:45:29.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T01:40:00.567Z"},{"id":"NVI-00012905","kind":"vulnerability","title":"Wasmtime: Preemption and traps during bulk operations enable breaking internal VM state","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-2hw9-mc66-jc2q","CVE-2026-104855"],"plain_summary":"GitHub lists this reviewed advisory for wasmtime, wasmtime. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2a1ba68d2f65661990ce1f36bdbcb291"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-06T17:17:16.000Z","value":"2 LOW (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-2a1ba68d2f65661990ce1f36bdbcb291"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0355cc9258f53060e442f9a38635174c","url":"https://github.com/advisories/GHSA-2hw9-mc66-jc2q","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2hw9-mc66-jc2q","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T01:40:00.567Z"},{"id":"sr-2a1ba68d2f65661990ce1f36bdbcb291","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-104855","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-104855","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:14.367Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0355cc9258f53060e442f9a38635174c"],"technology":"wasmtime","known_exclusions":[],"conditions_summary":"### Impact\n\nWasmtime's implementation of bulk-data-transfer WebAssembly instructions, such as `memory.copy`, contains a vulnerability when a preemption via epochs or fuel is combined with altering the store's state or cancelling a computation. To prevent these operations from taking too long Wasmtime injects fuel/epoch checks during these operations, but this enables embedders, and possible WebAssembly, to witness intermediate state in the middle of the operation. Examples of this include:\n\n* When a non-nullable WebAssembly table is grown the new elements initially start as null and are filled in as part of a loop with preemption checks. If this computation is then cancelled this left the table in a grown-but-uninitialized state where subsequent usage via WebAssembly could possibly segfault. Loads from this table are assumed to not be null due to its type, but the runtime implementation was exposed through this cancellation at a preemption point.\n* Embedders could mutate the store during an epoch callback, such as growing a WebAssembly linear memory. During a bulk `memory.copy` operation, however, the pointers being copied to/from weren't recomputed between preemption points. This ","public_affected_ranges":[">= 46.0.0, < 46.0.2"]},{"certainty":"source_listed","source_ids":["sr-0355cc9258f53060e442f9a38635174c"],"technology":"wasmtime","known_exclusions":[],"conditions_summary":"### Impact\n\nWasmtime's implementation of bulk-data-transfer WebAssembly instructions, such as `memory.copy`, contains a vulnerability when a preemption via epochs or fuel is combined with altering the store's state or cancelling a computation. To prevent these operations from taking too long Wasmtime injects fuel/epoch checks during these operations, but this enables embedders, and possible WebAssembly, to witness intermediate state in the middle of the operation. Examples of this include:\n\n* When a non-nullable WebAssembly table is grown the new elements initially start as null and are filled in as part of a loop with preemption checks. If this computation is then cancelled this left the table in a grown-but-uninitialized state where subsequent usage via WebAssembly could possibly segfault. Loads from this table are assumed to not be null due to its type, but the runtime implementation was exposed through this cancellation at a preemption point.\n* Embedders could mutate the store during an epoch callback, such as growing a WebAssembly linear memory. During a bulk `memory.copy` operation, however, the pointers being copied to/from weren't recomputed between preemption points. This ","public_affected_ranges":[">= 47.0.0, < 47.0.3"]}],"null_published_at":"2026-11-03T10:03:31.388Z","source_updated_at":"2026-10-02T22:45:30.000Z","source_disclosed_at":"2026-10-02T22:45:29.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-01T01:40:00.567Z"},{"id":"NVI-00012905","kind":"vulnerability","title":"Wasmtime: Preemption and traps during bulk operations enable breaking internal VM state","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2hw9-mc66-jc2q","CVE-2026-104855"],"plain_summary":"GitHub lists this reviewed advisory for wasmtime, wasmtime. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0355cc9258f53060e442f9a38635174c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0355cc9258f53060e442f9a38635174c","url":"https://github.com/advisories/GHSA-2hw9-mc66-jc2q","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2hw9-mc66-jc2q","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T01:40:00.567Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0355cc9258f53060e442f9a38635174c"],"technology":"wasmtime","known_exclusions":[],"conditions_summary":"### Impact\n\nWasmtime's implementation of bulk-data-transfer WebAssembly instructions, such as `memory.copy`, contains a vulnerability when a preemption via epochs or fuel is combined with altering the store's state or cancelling a computation. To prevent these operations from taking too long Wasmtime injects fuel/epoch checks during these operations, but this enables embedders, and possible WebAssembly, to witness intermediate state in the middle of the operation. Examples of this include:\n\n* When a non-nullable WebAssembly table is grown the new elements initially start as null and are filled in as part of a loop with preemption checks. If this computation is then cancelled this left the table in a grown-but-uninitialized state where subsequent usage via WebAssembly could possibly segfault. Loads from this table are assumed to not be null due to its type, but the runtime implementation was exposed through this cancellation at a preemption point.\n* Embedders could mutate the store during an epoch callback, such as growing a WebAssembly linear memory. During a bulk `memory.copy` operation, however, the pointers being copied to/from weren't recomputed between preemption points. This ","public_affected_ranges":[">= 46.0.0, < 46.0.2"]},{"certainty":"source_listed","source_ids":["sr-0355cc9258f53060e442f9a38635174c"],"technology":"wasmtime","known_exclusions":[],"conditions_summary":"### Impact\n\nWasmtime's implementation of bulk-data-transfer WebAssembly instructions, such as `memory.copy`, contains a vulnerability when a preemption via epochs or fuel is combined with altering the store's state or cancelling a computation. To prevent these operations from taking too long Wasmtime injects fuel/epoch checks during these operations, but this enables embedders, and possible WebAssembly, to witness intermediate state in the middle of the operation. Examples of this include:\n\n* When a non-nullable WebAssembly table is grown the new elements initially start as null and are filled in as part of a loop with preemption checks. If this computation is then cancelled this left the table in a grown-but-uninitialized state where subsequent usage via WebAssembly could possibly segfault. Loads from this table are assumed to not be null due to its type, but the runtime implementation was exposed through this cancellation at a preemption point.\n* Embedders could mutate the store during an epoch callback, such as growing a WebAssembly linear memory. During a bulk `memory.copy` operation, however, the pointers being copied to/from weren't recomputed between preemption points. This ","public_affected_ranges":[">= 47.0.0, < 47.0.3"]}],"null_published_at":"2026-11-01T07:29:12.901Z","source_updated_at":"2026-10-02T22:45:30.000Z","source_disclosed_at":"2026-10-02T22:45:29.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T01:40:00.567Z"}],"next_cursor":null,"snapshot_revision":"42594"}