Which versions of paragonie/random_compat are affected by GHSA-3FMQ-X9Q6-WM39?

paragonie/random_compat (composer) versions < 2.0 is affected.

Is there a fix for GHSA-3FMQ-X9Q6-WM39?

Yes. GHSA-3FMQ-X9Q6-WM39 is fixed in 2.0. Upgrade to this version or later.

Is GHSA-3FMQ-X9Q6-WM39 exploitable, and should I be worried?

Whether GHSA-3FMQ-X9Q6-WM39 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-3FMQ-X9Q6-WM39 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-3FMQ-X9Q6-WM39 in paragonie/random_compat

Q: What is GHSA-3FMQ-X9Q6-WM39?

GHSA-3FMQ-X9Q6-WM39 is a low-severity security vulnerability in paragonie/random_compat (composer), affecting versions < 2.0. It is fixed in 2.0.

Q: Is there a fix for GHSA-3FMQ-X9Q6-WM39?

Yes. GHSA-3FMQ-X9Q6-WM39 is fixed in 2.0. Upgrade to this version or later.

Q: Is GHSA-3FMQ-X9Q6-WM39 exploitable, and should I be worried?

Whether GHSA-3FMQ-X9Q6-WM39 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-3FMQ-X9Q6-WM39 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-3FMQ-X9Q6-WM39?

Upgrade paragonie/random_compat to 2.0 or later.

GHSA-3FMQ-X9Q6-WM39

GHSA-3FMQ-X9Q6-WM39 is a low-severity security vulnerability in paragonie/random_compat (composer), affecting versions < 2.0. It is fixed in 2.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

random_compat Uses insecure CSPRNG

random_compat versions prior to 2.0 are affected by a security vulnerability related to the insecure usage of Cryptographically Secure Pseudo-Random Number Generators (CSPRNG). The affected versions use openssl_random_pseudo_bytes(), which may result in insufficient entropy and compromise the security of generated random numbers.

Impact

Affected versions

paragonie/random_compat (< 2.0)

Security releases

paragonie/random_compat → 2.0 (composer)

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 paragonie/random_compat to 2.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-3FMQ-X9Q6-WM39? GHSA-3FMQ-X9Q6-WM39 is a low-severity security vulnerability in paragonie/random_compat (composer), affecting versions < 2.0. It is fixed in 2.0.
Which versions of paragonie/random_compat are affected by GHSA-3FMQ-X9Q6-WM39? paragonie/random_compat (composer) versions < 2.0 is affected.
Is there a fix for GHSA-3FMQ-X9Q6-WM39? Yes. GHSA-3FMQ-X9Q6-WM39 is fixed in 2.0. Upgrade to this version or later.
Is GHSA-3FMQ-X9Q6-WM39 exploitable, and should I be worried? Whether GHSA-3FMQ-X9Q6-WM39 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-3FMQ-X9Q6-WM39 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-3FMQ-X9Q6-WM39? Upgrade paragonie/random_compat to 2.0 or later.