Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-34871: n/a

0
Medium
VulnerabilityCVE-2026-34871cvecve-2026-34871
Published: Wed Apr 01 2026 (04/01/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

An issue was discovered in Mbed TLS before 3.6.6 and 4.x before 4.1.0 and TF-PSA-Crypto before 1.1.0. There is a Predictable Seed in a Pseudo-Random Number Generator (PRNG).

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/01/2026, 19:08:40 UTC

Technical Analysis

CVE-2026-34871 identifies a critical vulnerability in the Mbed TLS cryptographic library (versions before 3.6.6 and 4.x before 4.1.0) and TF-PSA-Crypto (before 1.1.0), where the pseudo-random number generator (PRNG) uses a predictable seed. PRNGs are essential for generating cryptographic keys, nonces, and other random values that ensure security properties such as confidentiality and integrity. A predictable seed compromises the unpredictability of the PRNG output, enabling attackers to potentially reproduce or predict cryptographic keys and session parameters. This can lead to the decryption of sensitive data, forging of digital signatures, or bypassing authentication mechanisms. The vulnerability is particularly severe in embedded systems and IoT devices, which often rely on Mbed TLS and TF-PSA-Crypto for secure communications and cryptographic functions. Since these devices are widely deployed in industrial control systems, consumer electronics, and critical infrastructure, the impact can be extensive. No public exploits have been reported yet, but the fundamental nature of the flaw makes it a high-risk issue. The lack of a CVSS score suggests this is a newly published vulnerability, and organizations should prioritize patching once updates are available. The root cause is insufficient entropy or flawed seed generation in the PRNG initialization process, which must be corrected to restore cryptographic strength.

Potential Impact

The impact of this vulnerability is significant as it undermines the core security guarantees of cryptographic operations relying on Mbed TLS and TF-PSA-Crypto. Predictable PRNG output can allow attackers to reconstruct cryptographic keys, decrypt confidential communications, impersonate legitimate devices, or inject malicious data. This threatens confidentiality, integrity, and potentially availability if attackers disrupt secure communications or authentication. Embedded and IoT devices affected by this flaw are often deployed in critical sectors such as industrial automation, healthcare, telecommunications, and defense, increasing the potential for widespread disruption and espionage. Organizations worldwide that depend on these libraries for secure communications or data protection face increased risk of compromise. The absence of known exploits currently limits immediate impact, but the vulnerability's nature means it could be weaponized rapidly once details are widely understood. Failure to address this flaw could lead to long-term exposure of sensitive data and erosion of trust in affected systems.

Mitigation Recommendations

To mitigate this vulnerability, organizations should: 1) Immediately identify all systems and devices using affected versions of Mbed TLS and TF-PSA-Crypto. 2) Apply patches or upgrade to Mbed TLS version 3.6.6 or later, or 4.1.0 or later, and TF-PSA-Crypto version 1.1.0 or later as soon as they become available. 3) For devices where patching is not feasible, consider compensating controls such as isolating affected devices from critical networks or limiting their communication scope. 4) Review and enhance entropy sources on embedded devices to ensure high-quality randomness for cryptographic operations. 5) Conduct cryptographic key rotation and reissue certificates or keys generated with vulnerable PRNG outputs to prevent reuse of compromised keys. 6) Implement monitoring for anomalous cryptographic failures or suspicious network activity that could indicate exploitation attempts. 7) Engage with vendors and suppliers to confirm remediation timelines and secure firmware updates. These steps go beyond generic advice by emphasizing inventory management, compensating controls, and cryptographic hygiene specific to embedded and IoT environments.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-03-31T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd69c0e6bfc5ba1deb9268

Added to database: 4/1/2026, 6:53:52 PM

Last enriched: 4/1/2026, 7:08:40 PM

Last updated: 4/3/2026, 1:03:19 PM

Views: 15

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses