CVE-2026-33662: OP-TEE optee_os · Integer Overflow or Wraparound
Affects OP-TEE optee_osSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Apr 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 29 Oct 2026.
What to do
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
Until an official fix is available, users should consider avoiding configurations with small RSA modulus sizes that could trigger the overflow or disabling RSA acceleration if feasible. Monitor vendor channels for updates and apply patches once released.
Description
CVE-2026-33662 is an integer overflow vulnerability in the OP-TEE optee_os versions 3.8.0 through 4.10. It occurs in the emsa_pkcs1_v1_5_encode() function when calculating padding size for RSA keys with small modulus values, leading to an underflow. This causes a memset() call to overwrite memory beyond intended bounds, resulting in a crash of OP-TEE. The issue affects only platforms that register RSA acceleration. The vulnerability has a CVSS score of 7.5 and is classified as high severity due to its potential to cause denial of service by crashing the trusted execution environment. No official patch or remediation guidance is currently provided by the vendor, and no known exploits are reported in the wild.