CVE-2026-44362

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-41911 (ENISA EUVD)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — 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. 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.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
7th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 every mission impact level.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: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (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.

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 6, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Jul 7, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Subkey 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-8v75

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
optee-os4.10.0-1 ... 4.9.0-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
optee-os4.10.0-1 ... 4.9.0-1 (6 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 35× 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 100 of 133 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. None are among the latest 100 rows. The 33 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-44362?
CVE-2026-44362 is a medium-severity vulnerability; its CVE record was published on July 6, 2026. 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…
When was the CVE record for CVE-2026-44362 published?
The CVE record for CVE-2026-44362 was published on July 6, 2026. 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 October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-44362 actively exploited?
CVE-2026-44362 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44362?
CVE-2026-44362 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44362?
The CVE record for CVE-2026-44362 names the fix: "Version 4.11.0 contains a patch."

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44362

Explore →

Is Your Infrastructure Affected by CVE-2026-44362?

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

Book a Demo →Browse All CVEs