CVE-2025-7394

What it is

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(), an additional code change was also made in wolfSSL to make RAND_bytes() behave similar to OpenSSL after a fork() call without calling RAND_poll(). Now the Hash-DRBG used gets reseeded after detecting running in a new process. If making use of RAND_bytes() and calling fork() we recommend updating to the latest version of wolfSSL. Thanks to Per Allansson from Appgate for the report.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2025-07-18 23:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 10:04 UTC Last updatedMost recent change to the record

Details

Published

2025-07-18 23:15 UTC

Last modified

2026-06-17 10:04 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-200 · Information exposure

Record status

Analyzed

Affected

• Wolfssl ≤ 5.8.0

Attack profile CVSS 4.0 · 7.0

Attack vector

Network

Complexity

High

Attack requirements

Present

Privileges needed

None

User interaction

Passive

Confidentiality

High

Integrity

None

Availability

None