Findings

CVE-2026-34874

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

Published Apr 1, 2026 · updated Jun 17, 2026 · trustedfirmware mbed tls

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.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 1, 2026 · NIST NVD

    Detected

    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.

  2. Jun 17, 2026 · NIST NVD

    Updated

    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.

Affected

  • cpe trustedfirmware/mbed tlsversion unspecified
  • cpe trustedfirmware/mbed tls4.0.0

Sources

  • CVE.orgVulnerability recordCVE-2026-34874

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-34874

    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.

    nvd.nist.gov

References

CVE-2026-34874 · ZeroDay Findings