Vulnerabilities

Vulnerability · CVE-2025-7394

In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values returned from RAND_byte

Published Jul 18, 2025 · catalog updated Jul 21, 2025 · wolfSSL wolfSSL

Check this week

CVE-2025-7394 is not in CISA KEV. FIRST estimates a 46.00% chance of exploitation in the next 30 days. Check whether you run wolfSSL wolfSSL.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
46.00%
Remediation
Vendor / distro source
Affected products
vendor wolfSSL wolfSSL 3.15.0 ≤5.8.0

In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values returned from RAND_bytes() after fork() is called. This can lead to weak or predictable random numbers generated in applications that are both using RAND_bytes() and doing fork() operations. This only affects applications explicitly calling RAND_bytes() after fork() and does not affect any internal TLS operations. Although RAND_bytes() documentation in OpenSSL calls out not being safe for use with fork() without first calling RAND_poll(),

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor wolfSSL wolfSSL 3.15.0 ≤5.8.03.15.0 ≤5.8.0

How to fix CVE-2025-7394

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2025-7394 is not in CISA KEV. FIRST estimates a 46.00% chance of exploitation in the next 30 days. Check whether you run wolfSSL wolfSSL.

Which versions are affected?

Compare what you have installed with wolfSSL wolfSSL 3.15.0 ≤5.8.0 3.15.0 ≤5.8.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 46.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 18, 2025 · EUVD

    Detected

    In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values returned from RAND_bytes() after fork() is called. This can lead to weak or predictable random numbers generated in applications that are both using RAND_bytes() and doing fork() operations. This only affects applications explicitly calling RA

  2. Jul 21, 2025 · EUVD

    Updated

    In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values returned from RAND_bytes() after fork() is called. This can lead to weak or predictable random numbers generated in applications that are both using RAND_bytes() and doing fork() operations. This only affects applications explicitly calling RA

Sources

  • CVE.orgVulnerability recordCVE-2025-7394

    Official CVE identifier

    cve.org
  • EUVDVulnerability recordEUVD-2025-21938

    In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values returned from RAND_bytes() after fork() is called. This can lead to weak or predictable random numbers generated in applica

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Jul 21, 2025. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.