CVE-2025-46733

HIGHNVD 7.97.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.9 under NVD CVSS v3. EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2025-20017 (ENISA EUVD)Source: ENISA EUVD

7.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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 version 4.5.0, using a specially crafted tee-supplicant binary running in REE userspace, an attacker can trigger a panic in a TA that uses the libutee Secure Storage API. Many functions in libutee, specifically those which make up the Secure Storage API, will panic if a system call returns an unexpected return code. This behavior is mandated by the TEE Internal Core API specification. However, in OP-TEE’s implementation, return codes of secure storage operations are passed through unsanitized from the REE tee-supplicant, through the Linux kernel tee-driver, through the OP-TEE kernel, back to libutee. Thus, an attacker with access to REE userspace, and the ability to stop tee-supplicant and replace it with their own process (generally trivial for a root user, and depending on the way permissions are set up, potentially available even to less privileged users) can run a malicious tee-supplicant process that responds to storage requests with unexpected response codes, triggering a panic in the requesting TA. This is particularly dangerous for TAs built with TA_FLAG_SINGLE_INSTANCE (corresponding to gpd.ta.singleInstance and TA_FLAG_INSTANCE_KEEP_ALIVE (corresponding to gpd.ta.keepAlive). The behavior of these TAs may depend on memory that is preserved between sessions, and the ability of an attacker to panic the TA and reload it with a clean memory space can compromise the behavior of those TAs. A critical example of this is the optee_ftpm TA. It uses the kept alive memory to hold PCR values, which crucially must be non-resettable. An attacker who can trigger a panic in the fTPM TA can reset the PCRs, and then extend them PCRs with whatever they choose, falsifying boot measurements, accessing sealed data, and potentially more. The impact of this issue depends significantly on the behavior of affected TAs. For some, it could manifest as a denial of service, while for others, like the fTPM TA, it can result in the disclosure of sensitive data. Anyone running the fTPM TA is affected, but similar attacks may be possible on other TAs that leverage the Secure Storage API. A fix is available in commit 941a58d78c99c4754fbd4ec3079ec9e1d596af8f.

CVSS v3
7.9
EG Score
7.9HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity79% × 45%
Impact severity (EG Severity): CVSS 7.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.9): severity, escalated by confirmed exploitation. This CVE's 7.9 is its impact severity (EG Severity), not escalated.

EG Severity
7.9 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 4, 2025

Last Modified

April 15, 2026

Advisory Details (2)

Auto-updated Sep 21, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

REE userspace code can panic TAs, leading to fTPM PCR reset and data disclosure · Advisory · OP-TEE/optee_os · GitHub

https://github.com/OP-TEE/optee_os/security/advisories/GHSA-f35r-hm2m-p6c3
GitHub commit

commit 941a58d78c99 (OP-TEE/optee_os)

Fix landed in OP-TEE/optee_os commit 941a58d78c99 — awaiting tagged release

https://github.com/OP-TEE/optee_os/commit/941a58d78c99c4754fbd4ec3079ec9e1d596af8f

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
optee-os—
  • every version up to 4.5.0-2: fixed in 4.5.0-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
optee-os—
  • every version up to 4.5.0-2: fixed in 4.5.0-2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 232 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 137 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-27 11:21 UTCEG score recompute
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-25 16:23 UTCEG score recompute
  12. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-18 05:31 UTCEG score recompute
  20. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-12 17:02 UTCEG score recompute
  25. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 70 more
  1. 2026-10-11 20:36 UTCEG score recompute
  2. 2026-10-11 18:47 UTCEG score recompute
  3. 2026-10-11 15:23 UTCEG score recompute
  4. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-06 17:28 UTCOSV refresh
  10. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  13. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  14. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  15. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  16. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  17. 2026-09-27 13:45 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  18. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  19. 2026-09-26 00:25 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  20. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  21. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-09-21 21:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  26. 2026-09-16 22:36 UTCOSV refresh
  27. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  28. 2026-09-15 03:09 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  29. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  30. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  31. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  32. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  33. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  34. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  35. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  36. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  37. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  38. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  39. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  40. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  41. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  42. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  43. 2026-08-28 22:43 UTCOSV refresh
  44. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  46. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  48. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-08-24 09:22 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  50. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  51. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  52. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  53. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  54. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  55. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  56. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  57. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  58. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  59. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  60. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  61. 2026-08-12 10:40 UTCOSV refresh
  62. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  63. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  64. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  65. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  66. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  67. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  68. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  69. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  70. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.1% · 4th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-46733?
CVE-2025-46733 is a high-severity vulnerability; its CVE record was published on July 4, 2025. 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 version 4.5.0, using a specially crafted tee-supplicant binary running in REE userspace, an attacker can trigger a panic in a TA that…
When was the CVE record for CVE-2025-46733 published?
The CVE record for CVE-2025-46733 was published on July 4, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-46733 actively exploited?
CVE-2025-46733 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-46733?
CVE-2025-46733 has a CVSS v3 base score of 7.9 (NVD).
How do I remediate CVE-2025-46733?
A fix for CVE-2025-46733 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-46733

Explore →

Is Your Infrastructure Affected by CVE-2025-46733?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs