# CVE-2026-41515: OP-TEE: RSA-OAEP padding oracle in NXP CAAM driver enables plaintext recovery

> An attacker can recover RSA-OAEP plaintext via a padding oracle in the NXP CAAM driver of OP-TEE, compromising encrypted data confidentiality.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/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:** 6 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-41515, GHSA-5q45-58r5-cq4g, UBUNTU-CVE-2026-41515

## What is CVE-2026-41515?

CVE-2026-41515 is a low-severity vulnerability in OP-TEE optee_os, published on 6 Jul 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. Starting in version 3.9.0 and prior to version 4.11.0, the RSA-OAEP decryption implementation in the NXP CAAM crypto driver uses non-constant-time `memcmp()` for label hash verification and has multiple distinguishable error paths. This creates a Manger-style padding oracle that allows an attacker to recover RSA-OAEP plaintext with approximately 1000-2000 adaptive chosen ciphertext queries. Version 4.11.0 contains a patch. As a workaround, disable the NXP CAAM RSA driver with `CFG_CRYPTO_DRV_RSA=n`.

Weakness: CWE-208 (Observable Timing Discrepancy)

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

It affects 1 product.


Products: Trustedfirmware Op-Tee.

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

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

## Is CVE-2026-41515 being exploited?

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

## 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-41515 and fix it if it is affected.

What it is: CVE-2026-41515 is a low-severity vulnerability in OP-TEE optee_os, published on 6 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41515 in the wild and no public exploit code.

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-41515/ (Markdown: https://insights.sbomify.com/CVE-2026-41515/index.md)
```

## Sources

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

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