cve.bz

CVE-2026-25834 trustedfirmware mbed tls: Improper Certificate Validation

6.5 mediumEPSS 0.1%

Medium (6.5) in trustedfirmware mbed tls. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
Mbed TLS v3.3.0 up to 3.6.5 and 4.0.0 allows Algorithm Downgrade.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th 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: partial, 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.
CWEs
CWE-295 Improper Certificate Validation
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
OWASP Top 10
A04:2025 Cryptographic Failures, A07:2025 Authentication Failures
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-25834 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-25834?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-25834?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-25834 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.3.0 before 3.6.6
trustedfirmware:mbed_tls4.0.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13mbedtls3.6.6-0.1~deb13u1DEBIAN-CVE-2026-25834
Debian14mbedtls3.6.6-0.1DEBIAN-CVE-2026-25834
Ubuntu16.04:LTS, 25.10, 26.04:LTS and 4 morembedtlsno fix listedUBUNTU-CVE-2026-25834
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0ovmf202502-160000.5.1SUSE-SU-2026:22016-1
openSUSELeap 16.0mbedtls3.6.6-bp160.1.1openSUSE-SU-2026:21144-1
openSUSETumbleweedmbedtls3.6.6-1.1openSUSE-SU-2026:10498-1
Alpinev3.20, v3.21, v3.22 and 1 morembedtls3.6.6-r0ALPINE-CVE-2026-25834
Alpinev3.24mbedtls, mbedtls33.6.6-r0ALPINE-CVE-2026-25834

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; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Moderate: This flaw in Mbed TLS allows a remote attacker to perform an algorithm downgrade attack, which can reduce the security strength of cryptographic operations. This could potentially lead to information disclosure or denial of service. This vulnerability affects community projects such as Fedora and EPEL.

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

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-97 Cryptanalysis Likelihood: Low · Severity: Very High
  • CAPEC-473 Signature Spoof
  • CAPEC-608 Cryptanalysis of Cellular Encryption Severity: High
  • CAPEC-614 Rooting SIM Cards Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON