CVE-2026-34875 json
An issue was discovered in Mbed TLS through 3.6.5 and TF-PSA-Crypto 1.0.0.
published 2026-04-01 7 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-17993
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- trustedfirmware mbed_tls 3.6.6
- trustedfirmware tf-psa-crypto 1.1.0
- mbedtls Debian 13 3.6.6-0.1~deb13u1
- mbedtls Debian 14 3.6.6-0.1
debian advisories DEBIAN-CVE-2026-34875
- mbedtls openSUSE Tumbleweed 3.6.6-1.1
opensuse advisories openSUSE-SU-2026:10498-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-34875 updated cvss 9.8
mbedtls: Mbed TLS and TF-PSA-Crypto: Arbitrary code execution due to buffer overflow in FFDH key export
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 7 mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Classification
- Weakness
-
- CWE-120 Buffer Copy without Checking Size of Input
References
Sources
- CVE List CVE-2026-34875
- NVD CVE-2026-34875
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.