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.20.0 and prior to version 4.11.0, a vulnerability in OP-TEE’s subkey rollback protection allows the use of revoked or older subkey versions because the system fails to propagate versioning data during the Trusted Application (TA) loading process. In core/crypto/signed_hdr.c, the function shdr_load_pub_key() parses subkey headers but does not assign the subkey_version to the runtime shdr_pub_key structure. As a result, the key->version field remains at zero regardless of the version specified in the header. When ree_fs_ta_open() in core/kernel/ree_fs_ta.c calls check_update_version(), it passes this zeroed version to the rollback database. Because the database never receives a non-zero version to record, it never advances, effectively bypassing the rollback check and allowing TAs signed with downgraded subkey chains to load successfully. This impacts OP-TEE mainline configurations that utilize subkey-based signing chains for Trusted Application (TA) authentication. Version 4.11.0 contains a patch. No known workarounds are available.
CVE-2026-44362
This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(medium)
- EPSS
- 2.4%
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 7, 2026
Advisory Details (1)
Auto-updated Jul 7, 2026Subkey rollback protection can be bypassed with older subkey versions · Advisory · OP-TEE/optee_os · GitHub
https://github.com/OP-TEE/optee_os/security/advisories/GHSA-fhcg-pp56-8v75Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 16:01 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 16:40 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 17:19 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 17:58 UTCEG score recompute
- 2026-07-08 18:36 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 19:15 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 19:47 UTCEG score recompute
- 2026-07-06 19:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-285
Frequently asked(5)
What is CVE-2026-44362?
When was CVE-2026-44362 disclosed?
Is CVE-2026-44362 actively exploited?
What is the CVSS score of CVE-2026-44362?
How do I remediate CVE-2026-44362?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-44362
Is Your Infrastructure Affected by CVE-2026-44362?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.