Predictable cryptographic keys via early-boot entropy fallback
Published Apr 1, 2026 · Updated Apr 1, 2026
Predictable entropy in Mbed TLS 3.6.5 and earlier, Mbed TLS 4.0.0, and TF-PSA-Crypto 1.0.0 allows attackers to predict keys. When getrandom() is unavailable or blocked, entropy_poll.c and platform_util.c read /dev/urandom without waiting for the Linux entropy pool to initialize. Exposure requires installation or early boot without sufficient saved or hardware entropy; predictable keys and randomized ECDSA nonces can compromise generated keys.
Summary
What happened
Predictable entropy in Mbed TLS 3.6.5 and earlier, Mbed TLS 4.0.0, and TF-PSA-Crypto 1.0.0 allows attackers to predict keys. When getrandom() is unavailable or blocked, entropy_poll.c and platform_util.c read /dev/urandom without waiting for the Linux entropy pool to initialize. Exposure requires installation or early boot without sufficient saved or hardware entropy; predictable keys and randomized ECDSA nonces can compromise generated keys.
The record
- CVE
- CVE-2026-34871
- Published
- Apr 1, 2026
- Updated
- Apr 1, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-338
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2026CVE publishedPublication date reported by the CVE source.
- Apr 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo