CVE-2025-27809

MEDIUMNVD 5.45.4—Trending — 5 sources updated this week

5.4

Mbed TLS before 2.28.10 and 3.x before 3.6.3, on the client side, accepts servers that have trusted certificates for arbitrary hostnames unless the TLS client application calls mbedtls_ssl_set_hostname.

CVSS v3: 5.4
EG Score: 5.4(medium)
EPSS: 33.9%
KEV: Not listed

Published

March 25, 2025

Last Modified

July 17, 2025

References (4)

cve@mitrehttps://github.com/Mbed-TLS/mbedtls/releases
cve@mitrehttps://mbed-tls.readthedocs.io/en/latest/security-advisories/mbedtls-security-advisory-2025-03-1/
af854a3a-2127-422b-91ae-364da2661108https://github.com/Mbed-TLS/mbedtls/issues/466
af854a3a-2127-422b-91ae-364da2661108https://mastodon.social/@bagder/114219540623402700

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-1188Insecure Default Initialization of Resource

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Microsoft MSRCCVE-2025-278092025-09-04
Mbed TLS before 2.28.10 and 3.x before 3.6.3, on the client side, accepts servers that have trusted certificates for arbitrary hostnames unless the TLS client application calls mbedtls_ssl_set_hostname.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-30 08:55 UTCEG score recompute
2026-05-30 08:55 UTCVendor advisory
2026-05-30 08:55 UTCGHSA enrichment
2026-05-29 17:50 UTCOSV refresh
2026-05-29 13:44 UTCepss_batch

Frequently asked(5)

What is CVE-2025-27809?

CVE-2025-27809 is a medium vulnerability published on March 25, 2025. Mbed TLS before 2.28.10 and 3.x before 3.6.3, on the client side, accepts servers that have trusted certificates for arbitrary hostnames unless the TLS client application calls mbedtlssslset_hostname.

When was CVE-2025-27809 disclosed?

CVE-2025-27809 was first published in the National Vulnerability Database on March 25, 2025, with the most recent update on July 17, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2025-27809 actively exploited?

CVE-2025-27809 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2025-27809?

CVE-2025-27809 has a CVSS v3 base score of 5.4 (NVD).

How do I remediate CVE-2025-27809?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-27809, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-27809

Explore →

Is Your Infrastructure Affected by CVE-2025-27809?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs