CVE-2026-44362

Trusted application downgrade via zeroed subkey version

Published Jul 6, 2026 · Updated Jul 6, 2026

Improper authorization in OP-TEE OS 3.20.0 through 4.10.0 allows local users to load trusted applications signed by revoked subkeys. The shdr_load_pub_key() function parses each subkey header without copying subkey_version into the runtime key, so check_update_version() always receives zero and never advances the rollback database. Exploitation requires local low-privileged access and a mainline configuration using subkey-based trusted-application signing, enabling replacement with a downgraded chain that bypasses revocation and breaks trusted-application integrity.

CVSS severity5.5
Medium
EPSS probability0.18%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authorization in OP-TEE OS 3.20.0 through 4.10.0 allows local users to load trusted applications signed by revoked subkeys. The shdr_load_pub_key() function parses each subkey header without copying subkey_version into the runtime key, so check_update_version() always receives zero and never advances the rollback database. Exploitation requires local low-privileged access and a mainline configuration using subkey-based trusted-application signing, enabling replacement with a downgraded chain that bypasses revocation and breaks trusted-application integrity.

The record

CVE
CVE-2026-44362
Published
Jul 6, 2026
Updated
Jul 6, 2026
Vendor
OP-TEE
Product
OP-TEE OS
Classifications
CWE-285
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 6, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 6, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 3.20.0, < 4.11.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

OP-TEE · OP-TEE OSversion=>= 3.20.0, < 4.11.0

Published CVSS scores

5.5GitHub, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-285Improper Authorization

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo