Skip to content
Systems

CVE-2026-71969

8.4
High
EPSS 0.13%Patch availableAug 11, 2026

OP-TEE RSA NOPAD buffer underwrite allows secure-world heap corruption

common questions

Is CVE-2026-71969 being exploited?

Not confirmed. CVE-2026-71969 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-71969?

CVE-2026-71969 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-71969?

Yes. A fix has been recorded for CVE-2026-71969. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-71969 affect?

CVE-2026-71969 affects OP-TEE OS <= 4.10.0, mbedTLS RSA NOPAD backend, NXP SE050 driver, ARM TrustZone-enabled devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71969?

Apply OP-TEE fix (commit 7b8b494) or vendor patch; vet/revoke untrusted TAs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OP-TEE OS <= 4.10.0mbedTLS RSA NOPAD backendNXP SE050 driverARM TrustZone-enabled devices
impact

A malicious Trusted Application can corrupt S-EL1 secure-world heap, enabling secure-world memory corruption, potential code execution or DoS in TrustZone.

action required

Immediate action required

affected versions
OP-TEE optee_os
  • affected<= 4.10.0
vendor says fixed in7b8b494e0a324cefec8ed386b7de413b44f1aaf3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free