Unrated

random_compat Uses insecure CSPRNG

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (paragonie/random_compat 2.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Packagist paragonie/random_compat
Affected
< 2.0
Fixed in
2.0

Sources

GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-3fmq-x9q6-wm39 lists affected ranges: Packagist paragonie/random_compat >=0 <2.0
VerifiedObserved 26 Oct 2026, 14:24 UTCStructured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation

Exploitation: No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS: not scored
EPSS: No dated EPSS signal available.

Source description

As published by the source; long descriptions are shortened.

randomcompat 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 opensslrandompseudobytes(), which may result in insufficient entropy and compromise the security of generated random numbers.

Dates and revisions

Published by the source: 17 May 2024, 23:27 UTC
Last modified by the source: 17 May 2024, 23:27 UTC
Source last checked: 26 Oct 2026, 14:24 UTC

Revision 1 · created · 26 Oct 2026
Published from ghsa record GHSA-3fmq-x9q6-wm39

Agent brief

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

# Patch Next advisory brief: GHSA-3fmq-x9q6-wm39

Advisory: random_compat Uses insecure CSPRNG
IDs: GHSA-3fmq-x9q6-wm39
Record: https://patchnext.com/advisories/ghsa-3fmq-x9q6-wm39 (revision 1, source checked 26 Oct 2026, 14:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: paragonie/random_compat 2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist paragonie/random_compat: affected < 2.0; fixed in 2.0

## Suggested inspection (read-only)
- Packagist paragonie/random_compat: 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 paragonie/random_compat.
- 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-3fmq-x9q6-wm39 (GitHub-reviewed advisory GHSA-3fmq-x9q6-wm39 lists affected ranges: Packagist paragonie/random_compat >=0 <2.0)

Commands are suggestions: review each one before running it.

Loading voting…