# CVE-2025-59438: Information disclosure in n/a

> An attacker can exploit timing discrepancies in Mbed TLS to potentially recover sensitive cryptographic information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Oct 2025
- **Updated:** 21 Oct 2025
- **Also known as:** ALPINE-CVE-2025-59438, DEBIAN-CVE-2025-59438, GHSA-mqc9-9p37-h763, JLSEC-2025-233, ROOT-OS-DEBIAN-12-CVE-2025-59438, SUSE-SU-2026:1413-1, SUSE-SU-2026:20769-1, SUSE-SU-2026:21018-1, SUSE-SU-2026:21161-1, UBUNTU-CVE-2025-59438, openSUSE-SU-2025:15662-1, openSUSE-SU-2025:20035-1, openSUSE-SU-2026:10083-1, openSUSE-SU-2026:10378-1, openSUSE-SU-2026:20499-1

## What is CVE-2025-59438?

CVE-2025-59438 is a medium-severity vulnerability in Arm Mbed Tls, published on 21 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mbed TLS through 3.6.4 has an Observable Timing Discrepancy.

Weakness: CWE-208 (Observable Timing Discrepancy)

## Which versions are affected by CVE-2025-59438?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ovmf` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 202408-150700.3.15.1 |
| `ovmf` | SUSE:Linux Enterprise Module for Server Applications 15 SP7 | All versions | 202408-150700.3.15.1 |
| `ovmf` | SUSE:Linux Enterprise Server 16.0 | All versions | 202502-160000.4.1 |
| `ovmf` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 202502-160000.4.1 |
| `ovmf` | SUSE:Linux Micro 6.1 | All versions | 202402-slfo.1.1_2.1 |
| `ovmf` | SUSE:Linux Micro 6.2 | All versions | 202502-160000.4.1 |
| `micropython` | openSUSE:Leap 16.0 | All versions | 1.26.0-bp160.1.1 |
| `ovmf` | openSUSE:Leap 16.0 | All versions | 202502-160000.4.1 |
| `micropython` | openSUSE:Tumbleweed | All versions | 1.26.0-2.1 |
| `ovmf` | openSUSE:Tumbleweed | All versions | 202602-5.1 |
| `vlang` | openSUSE:Tumbleweed | All versions | 0.5-2.1 |

Products: Arm Mbed Tls.

## How do I fix CVE-2025-59438?

Upgrade to a fixed version.

## Is CVE-2025-59438 being exploited?

There is no known exploitation of CVE-2025-59438 in the wild and no public exploit code.

## Other vulnerabilities in Arm Mbed Tls

- [CVE-2026-34877](https://insights.sbomify.com/CVE-2026-34877/): Deserialization in n/a (critical 9.8)
- [CVE-2022-46393](https://insights.sbomify.com/CVE-2022-46393/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-44732](https://insights.sbomify.com/CVE-2021-44732/): Use after free in n/a (critical 9.8)
- [CVE-2017-18187](https://insights.sbomify.com/CVE-2017-18187/): Integer overflow in n/a (critical 9.8)
- [CVE-2018-0487](https://insights.sbomify.com/CVE-2018-0487/): Memory corruption in ARM mbed TLS before 1.3.22, before 2.1.10, and before 2.7.0 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59438 and fix it if it is affected.

What it is: CVE-2025-59438 is a medium-severity vulnerability in Arm Mbed Tls, published on 21 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59438 in the wild and no public exploit code.

Affected product: Arm Mbed Tls. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59438/ (Markdown: https://insights.sbomify.com/CVE-2025-59438/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59438
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59438
- OSV: https://osv.dev/vulnerability/CVE-2025-59438

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59438/
Summaries are generated and may contain mistakes; the official description above is the record.