{"id":"CVE-2025-7394","aliases":["DEBIAN-CVE-2025-7394","EUVD-2025-21938","GHSA-jgh6-fqf6-cpj8","JLSEC-2026-689","UBUNTU-CVE-2025-7394"],"status":"published","title":"In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as...","description":"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.","severity":{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00459,"percentile":0.40062,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-200","CWE-338"],"published":"2025-07-18T22:34:23Z","modified":"2026-10-28T02:30:28Z","fixes":[{"ecosystem":"Debian:12","package":"wolfssl","fixed_in":["5.5.4-2+deb12u2"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"wolfssl","fixed_in":["5.7.2-0.1+deb13u1"],"sources":["osv"]},{"ecosystem":"Julia","package":"wolfSSL_jll","fixed_in":["5.8.4+0"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.5.4-2+deb12u2"}]}],"versions":["5.5.4-2","5.5.4-2+deb12u1"]},{"source":"osv","ecosystem":"Debian:13","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.7.2-0.1+deb13u1"}]}],"versions":["5.7.2-0.1"]},{"source":"osv","ecosystem":"Julia","package":"wolfSSL_jll","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.8.4+0"}]}]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.4.8+dfsg-1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.10.2+dfsg-2","3.12.0+dfsg-1","3.12.2+dfsg-1","3.13.0+dfsg-1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.1.0+dfsg-2","4.2.0+dfsg-1","4.2.0+dfsg-2","4.2.0+dfsg-3","4.3.0+dfsg-2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.6.0-3","5.0.0-1","5.1.1-1","5.2.0-1","5.2.0-2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.5.4-2","5.5.4-2.1","5.6.4-2","5.6.6-1.2","5.6.6-1.3","5.6.6-1.3build1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.7.2-0.1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.9.1-0.1","5.9.2-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.7.2-0.1","5.8.2-1.2","5.8.4-1","5.9.1-0.1"]}],"products":[{"vendor":"wolfssl","product":"wolfssl"}],"references":[{"url":"https://github.com/wolfSSL/wolfssl/blob/master/ChangeLog.md#wolfssl-release-582-july-17-2025","tags":["Release Notes","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-7394","tags":["advisory","web"]},{"url":"https://github.com/advisories/GHSA-jgh6-fqf6-cpj8","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/7xxx/CVE-2025-7394.json","tags":["advisory"]},{"url":"https://github.com/wolfssl/wolfssl","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2025-7394","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-7394","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-7394","tags":["report"]},{"url":"https://github.com/wolfSSL/wolfssl/pull/8849","tags":["report"]},{"url":"https://github.com/wolfSSL/wolfssl/pull/8867","tags":["report"]},{"url":"https://github.com/wolfSSL/wolfssl/pull/8898","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2025-7394","description":"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.","status":"published","published":"2025-07-18T22:34:23.849Z","modified":"2025-07-21T15:00:21.78Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","level":"high","assessor":"cna"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T14:32:51.199669Z"}],"euvd":[{"id":"EUVD-2025-21938","description":"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.","status":"published","published":"2025-07-18T22:34:23Z","modified":"2025-07-21T15:00:21Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","level":"high"}],"updated_at":"2026-11-02T20:32:06.504899Z"}],"ghsa":[{"id":"GHSA-jgh6-fqf6-cpj8","title":"In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as...","description":"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.","status":"published","published":"2025-07-19T00:32:31Z","modified":"2025-12-03T15:30:27Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high"},{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-200","CWE-338"],"updated_at":"2026-11-02T15:05:01.323335Z"}],"nvd":[{"id":"CVE-2025-7394","description":"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.","status":"published","published":"2025-07-18T23:15:23.47Z","modified":"2026-06-17T10:04:50.223Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"},{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary"}],"cwes":["CWE-200","CWE-338"],"updated_at":"2026-11-02T14:11:18.782156Z"}],"osv":[{"id":"CVE-2025-7394","description":"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.","status":"published","published":"2025-07-18T22:34:23.849Z","modified":"2026-10-28T02:30:28.776026525Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","level":"high"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T15:44:53.185592Z"},{"id":"DEBIAN-CVE-2025-7394","description":"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.","status":"published","published":"2025-07-18T23:15:23.47Z","modified":"2026-09-01T20:05:58.839457199Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:45:48.440897Z"},{"id":"JLSEC-2026-689","title":"In the OpenSSL compatibility layer implementation, the function `RAND_poll()` was not behaving as...","description":"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.","status":"published","published":"2026-07-14T21:41:35.775Z","modified":"2026-07-25T18:24:46.262095371Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"},{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high"}],"updated_at":"2026-11-02T15:47:19.003546Z"},{"id":"UBUNTU-CVE-2025-7394","description":"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.","status":"published","published":"2025-07-18T23:15:00Z","modified":"2026-10-17T12:57:33.653795514Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","level":"high"},{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T16:55:55.926217Z"}]}}