What is GHSA-PQPW-89W5-82V5?

GHSA-PQPW-89W5-82V5 is a medium-severity security vulnerability in simd-json-derive (rust), affecting versions < 0.12.0. It is fixed in 0.12.0.

Which versions of simd-json-derive are affected by GHSA-PQPW-89W5-82V5?

simd-json-derive (rust) versions < 0.12.0 is affected.

Is there a fix for GHSA-PQPW-89W5-82V5?

Yes. GHSA-PQPW-89W5-82V5 is fixed in 0.12.0. Upgrade to this version or later.

Is GHSA-PQPW-89W5-82V5 exploitable, and should I be worried?

Whether GHSA-PQPW-89W5-82V5 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-PQPW-89W5-82V5 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-PQPW-89W5-82V5 in simd-json-derive

Q: Which versions of simd-json-derive are affected by GHSA-PQPW-89W5-82V5?

simd-json-derive (rust) versions < 0.12.0 is affected.

Q: Is there a fix for GHSA-PQPW-89W5-82V5?

Yes. GHSA-PQPW-89W5-82V5 is fixed in 0.12.0. Upgrade to this version or later.

Q: Is GHSA-PQPW-89W5-82V5 exploitable, and should I be worried?

Whether GHSA-PQPW-89W5-82V5 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-PQPW-89W5-82V5 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-PQPW-89W5-82V5?

Upgrade simd-json-derive to 0.12.0 or later.

Summary

simd-json-derive vulnerable to MaybeUninit misuse

An invalid use of MaybeUninit::uninit().assume_init() in simd-json-derive's derive macro can cause undefined behavior. The original code used MaybeUninit to avoid initialisation of the struct and then set the fields using ptr::write. The undefined behavior triggered by this misuse of MaybeUninit can lead to invlaid memory access and panics in binaries compiled in release mode (aka simd-json-derive prior to version 0.12 has UB and optimizes into some nonsense)

The version 0.12.0 removes this section of code, avoiding the use of MaybeUninit alltogether.

Impact

Affected versions

simd-json-derive (< 0.12.0)

Security releases

simd-json-derive → 0.12.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 simd-json-derive to 0.12.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-PQPW-89W5-82V5? GHSA-PQPW-89W5-82V5 is a medium-severity security vulnerability in simd-json-derive (rust), affecting versions < 0.12.0. It is fixed in 0.12.0.
Which versions of simd-json-derive are affected by GHSA-PQPW-89W5-82V5? simd-json-derive (rust) versions < 0.12.0 is affected.
Is there a fix for GHSA-PQPW-89W5-82V5? Yes. GHSA-PQPW-89W5-82V5 is fixed in 0.12.0. Upgrade to this version or later.
Is GHSA-PQPW-89W5-82V5 exploitable, and should I be worried? Whether GHSA-PQPW-89W5-82V5 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-PQPW-89W5-82V5 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-PQPW-89W5-82V5? Upgrade simd-json-derive to 0.12.0 or later.