CVE-2026-34871

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).

Published: 2026-04-01 Last update: 2026-04-06 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-34871 is rated Low Risk (27.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-34871

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-02 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-34871

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.4 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-34871

OS Trackers for CVE-2026-34871

vendor priority summary link
debian unimportant CVE-2026-34871 unimportant priority: Debian including 1 source packages (mbedtls), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2026-34871
suse medium CVE-2026-34871 severity moderate: SUSE including 11 source package names (libeverest-3.6.6-1.1, libeverest-x86-64-v3-3.6.6-1.1, …), 11 product×package rows across 1 product lines (openSUSE Tumbleweed): Fixed 11. https://www.suse.com/security/cve/CVE-2026-34871/
ubuntu medium CVE-2026-34871 medium priority: Ubuntu including 1 source packages (mbedtls), 7 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): needs-triage 7. https://ubuntu.com/security/CVE-2026-34871

Affected software / configurations for CVE-2026-34871

Vendor Product Version Raw CPE
arm mbed_tls < 3.6.6 cpe:2.3:a:arm:mbed_tls:*:*:*:*:*:*:*:*
arm tf-psa-crypto < 1.1.0 cpe:2.3:a:arm:tf-psa-crypto:*:*:*:*:*:*:*:*

References for CVE-2026-34871

cvelogic Threat Intelligence