Key recovery via cloned random-generator state
Published Apr 1, 2026 · Updated Apr 1, 2026
Insufficient randomness in affected Mbed TLS and TF-PSA-Crypto releases allows attackers to recover keys from cloned instances. The PSA subsystem copies its internal random-generator state during fork, VM cloning, or repeated resume and lacks a forced-reseed interface, so clones initially emit the same keys, nonces, and other outputs. Exploitation requires cloned application state and access to output from one instance; knowledge of a public nonce can expose a victim instance's session key.
Summary
What happened
Insufficient randomness in affected Mbed TLS and TF-PSA-Crypto releases allows attackers to recover keys from cloned instances. The PSA subsystem copies its internal random-generator state during fork, VM cloning, or repeated resume and lacks a forced-reseed interface, so clones initially emit the same keys, nonces, and other outputs. Exploitation requires cloned application state and access to output from one instance; knowledge of a public nonce can expose a victim instance's session key.
The record
- CVE
- CVE-2026-25835
- Published
- Apr 1, 2026
- Updated
- Apr 1, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-335
- 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