static-alloc vulnerability leads to uninitialized read after allocating MemBump

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

0.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N/E:U · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

The affected function, MemBump::new(), would allocate memory without initializing it. Subsequently calling the created value's various allocmethods would then read and write the start of that memory as a Cell which isundefined behavior. Instead, it should zero initialize the start of the allocated memory. For instance, some values could violate the internal invariants of the type and cause an assertion failure. Nevertheless, no deterministic read is known tocause further uninitialized memory to be exposed. Affected downstream users that can not upgrade are advised to call MemBump::reset immediately after allocation to manually perform the missing write of the counter best-as-possible. The flaw was corrected in commit d8d6a7d096d3aaafd963b356a8f1bbd8d26fd967 by zeroing the Cell at the start of the allocated memory.

Published by the source

11 Jul 2025, 19:57 UTC

Last modified by the source

11 Jul 2025, 19:57 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xrrq-rrgq-h89w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-xrrq-rrgq-h89w

Advisory: static-alloc vulnerability leads to uninitialized read after allocating MemBump
IDs: GHSA-xrrq-rrgq-h89w
Record: https://patchnext.com/advisories/ghsa-xrrq-rrgq-h89w (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated (CVSS 0.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: static-alloc 0.2.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io static-alloc: affected >= 0.2.2, < 0.2.6; fixed in 0.2.6

## Suggested inspection (read-only)
- crates.io static-alloc: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on static-alloc.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xrrq-rrgq-h89w (GitHub-reviewed advisory GHSA-xrrq-rrgq-h89w lists affected ranges: crates.io static-alloc >=0.2.2 <0.2.6)

Commands are suggestions: review each one before running it.