OP-TEE optee_os up to 4.10.x on Arm X/Y signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 2.97- |
Summary
A vulnerability categorized as problematic has been discovered in OP-TEE optee_os up to 4.10.x on Arm. This affects an unknown part. Executing a manipulation of the argument X/Y can lead to signature verification. The identification of this vulnerability is CVE-2026-45614. The attack can only be executed locally. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in OP-TEE optee_os up to 4.10.x on Arm and classified as problematic. This vulnerability affects an unknown functionality. The manipulation of the argument X/Y with an unknown input leads to a signature verification vulnerability. The CWE definition for the vulnerability is CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. As an impact it is known to affect confidentiality. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability was named CVE-2026-45614 since 05/12/2026. The exploitation appears to be difficult. Local access is required to approach this attack. Technical details are known, but there is no available exploit.
Upgrading to version 4.11.0 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
Website
- Product: https://github.com/OP-TEE/optee_os/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.5
VulDB Base Score: 2.5
VulDB Temp Score: 2.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.7
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: optee_os 4.11.0
Timeline
05/12/2026 CVE reserved06/03/2026 Advisory disclosed
06/03/2026 VulDB entry created
06/03/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-g6qf-hwf7-mg9h
Status: Confirmed
CVE: CVE-2026-45614 (🔒)
GCVE (CVE): GCVE-0-2026-45614
GCVE (VulDB): GCVE-100-368194
Entry
Created: 06/03/2026 21:43Changes: 06/03/2026 21:43 (65)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.