cve.bz

CVE-2026-34875 trustedfirmware: Classic Buffer Overflow

9.8 criticalEPSS 0.4%

Critical (9.8) in trustedfirmware. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-04-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-120 Buffer Copy without Checking Size of Input (Classic Buffer Overflow)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-34875 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34875?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34875?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-34875 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
trustedfirmware:mbed_tlsfrom 3.5.0 before 3.6.6
trustedfirmware:tf-psa-cryptobefore 1.1.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12mbedtlsno fix listedDEBIAN-CVE-2026-34875
Debian13mbedtls3.6.6-0.1~deb13u1DEBIAN-CVE-2026-34875
Debian14mbedtls3.6.6-0.1DEBIAN-CVE-2026-34875
Ubuntu16.04:LTS, 25.10, 26.04:LTS and 3 morembedtlsno fix listedUBUNTU-CVE-2026-34875
openSUSETumbleweedmbedtls3.6.6-1.1openSUSE-SU-2026:10498-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Critical.

Red Hat's statement

Critical: A buffer overflow flaw in Mbed TLS and TF-PSA-Crypto during FFDH public key export could allow a remote attacker to execute arbitrary code or cause a denial of service. Red Hat products utilizing Mbed TLS for FFDH key operations are susceptible if they expose this functionality to untrusted input.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-34875.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-120 (13).

References

Check your stackJSON