Skip to content
IoT

CVE-2026-71968

8.4
High
EPSS 0.10%Patch availableAug 11, 2026

Use-after-free in OP-TEE loader allows secure-world kernel memory corruption.

common questions

Is CVE-2026-71968 being exploited?

Not confirmed. CVE-2026-71968 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.10% probability of exploitation in the next 30 days.

How severe is CVE-2026-71968?

CVE-2026-71968 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-71968?

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

What does CVE-2026-71968 affect?

CVE-2026-71968 affects OP-TEE OS <= 4.10.0, Devices using OP-TEE (ARM TrustZone TEEs), Signed Trusted Applications with TA_FLAG_CONCURRENT. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71968?

Update OP-TEE to commit 8794043+; apply vendor patches and audit/load policies for signed 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.0Devices using OP-TEE (ARM TrustZone TEEs)Signed Trusted Applications with TA_FLAG_CONCURRENT
impact

An attacker able to load a signed Trusted Application can corrupt S-EL1 secure-world kernel memory, potentially enabling TEE compromise or privilege escalation.

action required

Patch when possible

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

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