What is GHSA-2326-PFPJ-VX3H?

GHSA-2326-PFPJ-VX3H is a low-severity security vulnerability in lexical-core (rust), affecting versions < 1.0.0. It is fixed in 1.0.0.

Which versions of lexical-core are affected by GHSA-2326-PFPJ-VX3H?

lexical-core (rust) versions < 1.0.0 is affected.

Is there a fix for GHSA-2326-PFPJ-VX3H?

Yes. GHSA-2326-PFPJ-VX3H is fixed in 1.0.0. Upgrade to this version or later.

Is GHSA-2326-PFPJ-VX3H exploitable, and should I be worried?

Whether GHSA-2326-PFPJ-VX3H 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-2326-PFPJ-VX3H 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-2326-PFPJ-VX3H in lexical-core

Q: Which versions of lexical-core are affected by GHSA-2326-PFPJ-VX3H?

lexical-core (rust) versions < 1.0.0 is affected.

Q: Is there a fix for GHSA-2326-PFPJ-VX3H?

Yes. GHSA-2326-PFPJ-VX3H is fixed in 1.0.0. Upgrade to this version or later.

Q: Is GHSA-2326-PFPJ-VX3H exploitable, and should I be worried?

Whether GHSA-2326-PFPJ-VX3H 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-2326-PFPJ-VX3H 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-2326-PFPJ-VX3H?

Upgrade lexical-core to 1.0.0 or later.

Summary

lexical-core has multiple soundness issues

RUSTSEC-2024-0377 contains multiple soundness issues:

Bytes::read() allows creating instances of types with invalid bit patterns
BytesIter::read() advances iterators out of bounds
The BytesIter trait has safety invariants but is public and not marked unsafe
write_float() calls MaybeUninit::assume_init() on uninitialized data, which is is not allowed by the Rust abstract machine
radix() calls MaybeUninit::assume_init() on uninitialized data, which is is not allowed by the Rust abstract machine

Version 1.0 fixes these issues, removes the vast majority of unsafe code, and also fixes some correctness issues.

Impact

Affected versions

lexical-core (< 1.0.0)

Security releases

lexical-core → 1.0.0 (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 lexical-core to 1.0.0 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-2326-PFPJ-VX3H? GHSA-2326-PFPJ-VX3H is a low-severity security vulnerability in lexical-core (rust), affecting versions < 1.0.0. It is fixed in 1.0.0.
Which versions of lexical-core are affected by GHSA-2326-PFPJ-VX3H? lexical-core (rust) versions < 1.0.0 is affected.
Is there a fix for GHSA-2326-PFPJ-VX3H? Yes. GHSA-2326-PFPJ-VX3H is fixed in 1.0.0. Upgrade to this version or later.
Is GHSA-2326-PFPJ-VX3H exploitable, and should I be worried? Whether GHSA-2326-PFPJ-VX3H 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-2326-PFPJ-VX3H 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-2326-PFPJ-VX3H? Upgrade lexical-core to 1.0.0 or later.