What is GHSA-XRRQ-RRGQ-H89W?

GHSA-XRRQ-RRGQ-H89W is a low-severity security vulnerability in static-alloc (rust), affecting versions >= 0.2.2, < 0.2.6. It is fixed in 0.2.6.

Which versions of static-alloc are affected by GHSA-XRRQ-RRGQ-H89W?

static-alloc (rust) versions >= 0.2.2, < 0.2.6 is affected.

Is there a fix for GHSA-XRRQ-RRGQ-H89W?

Yes. GHSA-XRRQ-RRGQ-H89W is fixed in 0.2.6. Upgrade to this version or later.

Is GHSA-XRRQ-RRGQ-H89W exploitable, and should I be worried?

Whether GHSA-XRRQ-RRGQ-H89W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-XRRQ-RRGQ-H89W is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-XRRQ-RRGQ-H89W in static-alloc

Q: Which versions of static-alloc are affected by GHSA-XRRQ-RRGQ-H89W?

static-alloc (rust) versions >= 0.2.2, < 0.2.6 is affected.

Q: Is there a fix for GHSA-XRRQ-RRGQ-H89W?

Yes. GHSA-XRRQ-RRGQ-H89W is fixed in 0.2.6. Upgrade to this version or later.

Q: Is GHSA-XRRQ-RRGQ-H89W exploitable, and should I be worried?

Whether GHSA-XRRQ-RRGQ-H89W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-XRRQ-RRGQ-H89W is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-XRRQ-RRGQ-H89W?

Upgrade static-alloc to 0.2.6 or later.

Summary

static-alloc vulnerability leads to uninitialized read after allocating MemBump

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.

Impact

Affected versions

static-alloc (>= 0.2.2, < 0.2.6)

Security releases

static-alloc → 0.2.6 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade static-alloc to 0.2.6 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-XRRQ-RRGQ-H89W? GHSA-XRRQ-RRGQ-H89W is a low-severity security vulnerability in static-alloc (rust), affecting versions >= 0.2.2, < 0.2.6. It is fixed in 0.2.6.
Which versions of static-alloc are affected by GHSA-XRRQ-RRGQ-H89W? static-alloc (rust) versions >= 0.2.2, < 0.2.6 is affected.
Is there a fix for GHSA-XRRQ-RRGQ-H89W? Yes. GHSA-XRRQ-RRGQ-H89W is fixed in 0.2.6. Upgrade to this version or later.
Is GHSA-XRRQ-RRGQ-H89W exploitable, and should I be worried? Whether GHSA-XRRQ-RRGQ-H89W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-XRRQ-RRGQ-H89W is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-XRRQ-RRGQ-H89W? Upgrade static-alloc to 0.2.6 or later.