CVE-2024-49195

Mbed TLS 3.5.x through 3.6.x before 3.6.2 has a buffer underrun in pkwrite when writing an opaque key pair

Published: 2024-10-15 Last update: 2026-06-05 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-49195 is rated High Risk (66.3/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.00%). High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-49195

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-06 0.73% 1.00% +0.26%
2 2025-12-31 0.61% 0.73% +0.13%
3 2025-12-04 — 0.61% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-49195

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-49195

OS Trackers for CVE-2024-49195

vendor priority summary link
alpine — CVE-2024-49195: 1 source package rows (mbedtls); 8 state rows across 4 repos (3.20-main, 3.21-main, 3.22-main, edge-main); fixed 4, open 4. https://security.alpinelinux.org/vuln/CVE-2024-49195
debian unimportant CVE-2024-49195 unimportant priority: Debian including 1 source packages (mbedtls), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-49195
suse high CVE-2024-49195 severity important: SUSE including 71 source package names (libeverest-3.6.2-1.1, libeverest-x86-64-v3-3.6.2-1.1, …), 880 product×package rows across 40 product lines (SUSE Linux Enterprise High Performance Computing 12 SP5, SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS, … (40 product lines)): Known Not Affected 869, Fixed 11. https://www.suse.com/security/cve/CVE-2024-49195/
ubuntu medium CVE-2024-49195 medium priority: Ubuntu including 1 source packages (mbedtls), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): not-affected 7, ignored 1, released 1. https://ubuntu.com/security/CVE-2024-49195

Affected software / configurations for CVE-2024-49195

Vendor Product Version Raw CPE
trustedfirmware mbed_tls >= 3.5.0, < 3.6.2 cpe:2.3:a:trustedfirmware:mbed_tls:*:*:*:*:*:*:*:*

References for CVE-2024-49195

cvelogic Threat Intelligence