CVE-2025-46733Public exploit

Trusted application state reset via unsanitized return codes

Published Jul 4, 2025 · Updated Jul 7, 2025

Improper exceptional-condition handling in OP-TEE OS 4.5.0 allows local users to reset trusted application state via a malicious tee-supplicant. libutee Secure Storage functions pass unexpected return codes from the REE tee-supplicant through the kernel without sanitization, causing the requesting trusted application to panic. The attacker must be able to stop and replace tee-supplicant; resetting a persistent fTPM trusted application clears PCRs, permits forged boot measurements, and exposes PCR-sealed data.

CVSS severity7.9
High
EPSS probability0.14%
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 exceptional-condition handling in OP-TEE OS 4.5.0 allows local users to reset trusted application state via a malicious tee-supplicant. libutee Secure Storage functions pass unexpected return codes from the REE tee-supplicant through the kernel without sanitization, causing the requesting trusted application to panic. The attacker must be able to stop and replace tee-supplicant; resetting a persistent fTPM trusted application clears PCRs, permits forged boot measurements, and exposes PCR-sealed data.

The record

CVE
CVE-2025-46733
Published
Jul 4, 2025
Updated
Jul 7, 2025
Vendor
OP-TEE
Product
OP-TEE OS
Classifications
CWE-755, T1562.001
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 4, 2025CVE publishedPublication date reported by the CVE source.
  2. Jul 7, 2025Record 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== 4.5.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

OP-TEE · OP-TEE OSversion== 4.5.0

Published CVSS scores

7.9GitHubCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

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 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-755Improper Handling of Exceptional Conditions
T1562.001Impair Defenses: Disable or Modify Tools

Public exploit references

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