CVE-2026-34875

An issue was discovered in Mbed TLS through 3.6.5 and TF-PSA-Crypto 1.0.0. A buffer overflow can occur in public key export for FFDH keys.

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

CVE-2026-34875 is rated Moderate Risk (49.4/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.37%). Review affected assets and schedule remediation.

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-34875

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-06-15 0.05% 0.37% +0.31%
2 2026-04-07 0.04% 0.05% +0.01%
3 2026-04-02 — 0.04% —

Full EPSS history (3 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
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:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-34875

OS Trackers for CVE-2026-34875

vendor priority summary link
debian not yet assigned CVE-2026-34875 not yet assigned priority: Debian including 1 source packages (mbedtls), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-34875
redhat critical — https://access.redhat.com/security/cve/CVE-2026-34875
suse critical CVE-2026-34875 severity critical: 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-34875/
ubuntu medium CVE-2026-34875 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-34875

Affected software / configurations for CVE-2026-34875

Vendor Product Version Raw CPE
trustedfirmware mbed_tls >= 3.5.0, < 3.6.6 cpe:2.3:a:trustedfirmware:mbed_tls:*:*:*:*:*:*:*:*
trustedfirmware tf-psa-crypto < 1.1.0 cpe:2.3:a:trustedfirmware:tf-psa-crypto:*:*:*:*:*:*:*:*

References for CVE-2026-34875

cvelogic Threat Intelligence