# CVE-2026-45614: OP-TEE vulnerable to ECDH private key recovery

> An attacker can recover ECDH private keys from OP-TEE by sending crafted public keys that bypass curve validation, compromising secure communications.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-45614, GHSA-g6qf-hwf7-mg9h, UBUNTU-CVE-2026-45614

## What is CVE-2026-45614?

CVE-2026-45614 is a medium-severity vulnerability in OP-TEE optee_os, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OP-TEE is a Trusted Execution Environment (TEE) designed as companion to a non-secure Linux kernel running on Arm; Cortex-A cores using the TrustZone technology. Prior to version 4.11.0, on many of the ECDH shared secret paths, the public key isn't verified to be a point on the correct curve. By passing approximately 30-40 crafted public keys to OP-TEE, the private key can be reconstructed by a normal world attacker. When calling TEE_DeriveKey the public key is provided with full X and Y values, but the (X, Y) point might not satisfy the `Y^2 == X^3 + aX + b mod P` math for the specific curve that is used. When those public keys aren't rejected, the attacker can select public keys such that each DeriveKey call will leak `d % r` where `d` is the private key and `r` comes from the relationship between the correct curve and the attacker selected curve. With enough leaked data the Chinese remainder theorem can be used to recover the full private key. Version 4.11.0 fixes the issue.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-45614?

It affects 1 product.


Products: Trustedfirmware Op-Tee.

## How do I fix CVE-2026-45614?

No fix has been published for CVE-2026-45614 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45614 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45614 exists.

## Other vulnerabilities in OP-TEE optee_os

- [CVE-2019-1010292](https://insights.sbomify.com/CVE-2019-1010292/): Memory corruption in OP-TEE (critical 9.8)
- [CVE-2019-1010293](https://insights.sbomify.com/CVE-2019-1010293/): Memory corruption in OP-TEE (critical 9.8)
- [CVE-2019-1010295](https://insights.sbomify.com/CVE-2019-1010295/): Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Buffer Overflow. (critical 9.8)
- [CVE-2019-1010296](https://insights.sbomify.com/CVE-2019-1010296/): Memory corruption in OP-TEE (critical 9.8)
- [CVE-2019-1010297](https://insights.sbomify.com/CVE-2019-1010297/): Memory corruption in OP-TEE (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45614 and fix it if it is affected.

What it is: CVE-2026-45614 is a medium-severity vulnerability in OP-TEE optee_os, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45614 exists.

Affected product: OP-TEE optee_os. 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-2026-45614/ (Markdown: https://insights.sbomify.com/CVE-2026-45614/index.md)
```

## Sources

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

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