cve.bz

CVE-2025-52497 arm mbed tls: Off-by-one Error

4.8 mediumEPSS 0.3%

Medium (4.8) in arm mbed tls. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Mbed TLS before 3.6.4 has a PEM parsing one-byte heap-based buffer underflow, in mbedtls_pem_read_buffer and two mbedtls_pk_parse functions, via untrusted PEM input.

Severity

CVSS 3.1

4.8 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th 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: no · Technical impact: partial, assessed 2025-07-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-193 Off-by-one Error
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-52497 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-52497?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-52497?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-2025-52497 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 CNA's record in the CVE List.

ProductAffected
mbedtlsbefore 3.6.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11mbedtls2.16.9-0.1+deb11u2DLA-4274-1
Debian12mbedtlsno fix listedDEBIAN-CVE-2025-52497
Debian13, 14mbedtls3.6.4-1DEBIAN-CVE-2025-52497
Ubuntu16.04:LTS, 25.10mbedtlsno fix listedUBUNTU-CVE-2025-52497
UbuntuPro:18.04:LTSmbedtls2.8.0-1ubuntu0.1~esm1UBUNTU-CVE-2025-52497 USN-8123-1
UbuntuPro:20.04:LTSmbedtls2.16.4-1ubuntu2+esm1UBUNTU-CVE-2025-52497 USN-8123-1
UbuntuPro:22.04:LTSmbedtls2.28.0-1ubuntu0.1~esm1UBUNTU-CVE-2025-52497 USN-8123-1
UbuntuPro:24.04:LTSmbedtls2.28.8-1ubuntu0.1~esm1UBUNTU-CVE-2025-52497 USN-8123-1
openSUSELeap 16.0mbedtls3.6.6-bp160.1.1openSUSE-SU-2026:21144-1
Alpinev3.20, v3.21, v3.22 and 1 morembedtls3.6.4-r0ALPINE-CVE-2025-52497
Alpinev3.24mbedtls, mbedtls33.6.4-r0ALPINE-CVE-2025-52497

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 · openSUSE · Alpine.

References

Check your stackJSON