Skip to content
Fencer Intel
high 7.5

CVE-2026-34874 json

An issue was discovered in Mbed TLS through 3.6.5 and 4.x through 4.0.0.

published 7mo ago modified 4mo ago also EUVD-2026-18003

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

An issue was discovered in Mbed TLS through 3.6.5 and 4.x through 4.0.0. There is a NULL pointer dereference in distinguished name parsing that allows an attacker to write to address 0.

Patch / fix

  • trustedfirmware mbed_tls 3.6.6
  • mbedtls Debian 13 3.6.6-0.1~deb13u1
  • mbedtls Debian 14 3.6.6-0.1

debian advisories DEBIAN-CVE-2026-34874

  • ovmf SLES for SAP applications 16.0, SLES 16.0 202502-160000.5.1

suse advisories SUSE-SU-2026:22016-1

  • ovmf openSUSE Tumbleweed 202602-9.1
  • mbedtls openSUSE Tumbleweed 3.6.6-1.1

opensuse advisories openSUSE-SU-2026:10615-1openSUSE-SU-2026:10498-1

Is CVE-2026-34874 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-34874 updated cvss 7.5

mbedtls: NULL pointer dereference when setting a distinguished name

  • Red Hat All currently supported Red Hat products
    not 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
no
Technical impact
partial
Assessed
7mo ago

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Classification

Weakness

References

Sources

Fencer Intel 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.