CVE-2026-53763: OP-TEE optee_os · Integer Overflow or Wraparound
Affects OP-TEE optee_osSource CVE Database V5
Not known to be exploited · CVSS 3.8 Low : upgrade to 4.11.0 when convenient.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.11.0
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade optee_os and op-tee/optee_os to 4.11.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OP-TEEoptee_os | Affected
| Fixed in
|
GitHubop-tee/optee_ospkg:github/op-tee/optee_osOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade OP-TEE optee_os to version 4.11.0 or later, which contains a patch for this integer overflow vulnerability. No known workarounds exist. Users should apply this official fix to ensure correct AES-GCM authentication tag computation.
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.0.0 and prior to version 4.11.0, 32-bit integer overflows in OP-TEE core's AES-GCM implementation cause the authentication tag to be computed with incorrect bit-length values after processing more than 512 megabytes of payload or Additional Authenticated Data (AAD). Version 4.11.0 contains a patch. No known workarounds are available.