In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading
Source GCVE Database
Not known to be exploited · CVSS 9.8 Critical.
Data as of 22 Nov 2026, 03:02 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
AI-suggested
Update to the latest version of wolfSSL where the RAND_bytes() function reseeds the Hash-DRBG after fork(), mitigating the risk of predictable random numbers. This update aligns wolfSSL behavior with OpenSSL's documented requirement to call RAND_poll() after fork(). No other mitigation is indicated.
Description
A vulnerability in the OpenSSL compatibility layer of wolfSSL causes the RAND_poll() function to behave unexpectedly, potentially leading to predictable random numbers from RAND_bytes() after a fork() call. This affects applications that explicitly call RAND_bytes() after fork(), but does not impact internal TLS operations. wolfSSL has updated its implementation to reseed the Hash-DRBG after fork() to align with OpenSSL behavior. Users relying on RAND_bytes() with fork() should update to the latest wolfSSL version to mitigate this issue.