CVE-2026-25832: Low severity Mbed TLS Mbed TLS vulnerability

Published Sep 14, 2026
·
Updated

In Mbed TLS 3.6.x before 3.6.7 and 4.1.x before 4.1.2, the TLS 1.3 client accepts HelloRetryRequest selecting an unadvertised group.

Affected Software

2 affected components
Mbed TLS Mbed TLS<3.6.7
Mbed TLS Mbed TLS<4.1.2

Event History

Sep 14, 2026
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Deployments using Mbed TLS as a TLS 1.3 client are affected if they run Mbed TLS 3.6.x before 3.6.7 or 4.1.x before 4.1.2. The issue concerns processing of HelloRetryRequest messages.

2

What does exploitation require?

The vulnerability is network-reachable and requires no privileges or user interaction, but it has high attack complexity. Exploitation depends on getting the client to accept a HelloRetryRequest that selects a group the client did not advertise.

3

What should be done to remediate it?

Upgrade Mbed TLS 3.6.x to 3.6.7 or later, or upgrade Mbed TLS 4.1.x to 4.1.2 or later.

4

How can I determine whether an instance is exposed?

Check the deployed Mbed TLS version and whether the application operates as a TLS 1.3 client. Versions earlier than 3.6.7 in the 3.6.x line and earlier than 4.1.2 in the 4.1.x line are affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203