CVE-2026-25833

Mbed TLS 3.5.0 to 3.6.5 fixed in 3.6.6 and 4.1.0 has a buffer overflow in the x509_inet_pton_ipv6() function

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

CVE-2026-25833 is rated Low Risk (35.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.05%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-2026-25833

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-05-03 0.04% 0.05% +0.01%
2 2026-04-02 — 0.04% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-25833

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-25833

OS Trackers for CVE-2026-25833

vendor priority summary link
alpine — CVE-2026-25833: 1 source package rows (mbedtls); 5 state rows across 5 repos (3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 5, open 0. https://security.alpinelinux.org/vuln/CVE-2026-25833
debian unimportant CVE-2026-25833 unimportant priority: Debian including 1 source packages (mbedtls), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-25833
suse high CVE-2026-25833 severity important: SUSE including 79 source package names (libeverest-3.6.6-1.1, libeverest-x86-64-v3-3.6.6-1.1, …), 814 product×package rows across 28 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS, … (28 product lines)): Known Not Affected 803, Fixed 11. https://www.suse.com/security/cve/CVE-2026-25833/
ubuntu medium CVE-2026-25833 medium priority: Ubuntu including 1 source packages (mbedtls), 7 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): needs-triage 7. https://ubuntu.com/security/CVE-2026-25833

Affected software / configurations for CVE-2026-25833

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

References for CVE-2026-25833

cvelogic Threat Intelligence