How to Fix CVE-2026-33317: CWE-125: Out-of-bounds Read in optee_os
By Sai Kiran Pandrala
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-34987: Out-of-bounds read in wasmtime — Out-of-bounds read in wasmtime
- How to Fix CVE-2026-8758: Unrestricted File Upload in MetaCRM — Unrestricted File Upload in MetaCRM
- How to Fix CVE-2026-26226: Critical Vulnerability in beautiful-mermaid , Critical Vulnerability in beautiful-mermaid
- How to Fix CVE-2026-33884: Access Control Bypass in cms , Access Control Bypass in cms
- How to Fix CVE-2026-28788: Critical Vulnerability in open-webui , Critical Vulnerability in open-webui
Last verified: 2026-05-25
CVE-2026-33317 is a cwe-125: out-of-bounds read in OP-TEE optee_os. Fix it by upgrading to the patched build from the vendor advisory.
| Severity | CVSS 8.7 - High |
|---|---|
| Actively exploited? | Not currently in the CISA KEV catalog |
| Affected | optee_os >= 3.13.0, <= 4.10.0 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-125: CWE-125: Out-of-bounds Read |
What is CVE-2026-33317?
CVE-2026-33317 is a cwe-125: out-of-bounds read flaw in OP-TEE optee_os. It carries a CVSS base score of 8.7 (high). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
From the source record: 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. In versions 3.13.0 through 4.10.0, missing checks in entry_get_attribute_value() in ta/pkcs11/src/object.c can lead to out-of-bounds read from the PKCS#11 TA heap or a crash. When chained with the OOB read, the PKCS#11 TA function PKCS11_CMD_GET_ATTRIBUTE_VALUE or entry_get_attribute_value() can, with a bad template parameter, be tricked into reading at most 7 bytes beyond the end of the template buffer and writing beyond the end of the template buffer with the content of an attribute value of a PKCS#11 object. Commits e031c4e562023fd9f199e39fd2e85797e4cbdca9, 16926d5a46934c46e6656246b4fc18385a246900, and 149e8d7ecc4ef8bb00ab4a37fd2ccede6d79e1ca contain patches and are anticipated to be part of version 4.11.0.
Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.
Am I affected?
You are affected if your installation of optee_os matches a version listed in the Affected row above.
Check the running version against the Affected row above using the product's admin console or --version flag.
How to fix CVE-2026-33317
Apply the vendor patch. Target the build named in the Fixed in row above (See vendor advisory). The runnable command set below covers the most common deployment patterns for optee_os.
Generic upgrade pattern
If the affected product is a Linux package, upgrade via the system package manager:
# Debian / Ubuntu
sudo apt-get update && sudo apt-get upgrade -y
# RHEL / Rocky / Alma
sudo dnf upgrade --security -y
If it ships as a Windows installer, download the patched build from the vendor advisory and:
# Vendor advisory: https://github.com/OP-TEE/optee_os/security/advisories/GHSA-8cqw-mg7v-c9p9
Start-Process msiexec.exe -ArgumentList '/i <patched-installer>.msi /qn /norestart' -Wait
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | \
Where-Object DisplayName -match '<product-name>' | Select-Object DisplayName, DisplayVersion
After applying the patch
- Restart the service or device so the patched binary loads.
- Confirm the running version matches the Fixed in row using the verification command below.
- Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.
If you can't patch immediately
Until the patch lands, narrow the attack surface with these runnable controls.
Restrict network exposure
Block public access to the affected service at the perimeter. Allow only trusted source IPs.
# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4
# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
-RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny" -Direction Inbound -Action Block `
-Protocol TCP -LocalPort 443
Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.
How to verify the fix worked
Confirm the patched build is the one actually running.
Check the running version against the Affected row above using the product's admin console or --version flag.
Expected: a version at or above the patched build named in the vendor advisory.
Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.
Frequently asked questions
Is CVE-2026-33317 being exploited in the wild?
As of 2026-05-25, CVE-2026-33317 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.
What is the CVSS score for CVE-2026-33317?
The CVSS base score is 8.7 (High).
What version fixes this?
The vendor advisory names the patched build. See the References section.
Will a WAF or IDS rule alone close this?
No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.
References
- Official vendor advisory: https://github.com/OP-TEE/optee_os/security/advisories/GHSA-8cqw-mg7v-c9p9
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-33317
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://github.com/OP-TEE/optee_os/commit/149e8d7ecc4ef8bb00ab4a37fd2ccede6d79e1ca
- Additional reference: https://github.com/OP-TEE/optee_os/commit/16926d5a46934c46e6656246b4fc18385a246900
- Additional reference: https://github.com/OP-TEE/optee_os/commit/e031c4e562023fd9f199e39fd2e85797e4cbdca9
*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*