CVE-2025-10263

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.1Exploit: NoneExposed: 0

A fix is available — apply it.

Arm C1-Ultra, C1-Premium, Neoverse V3 & V3AE, Neoverse V2, Neoverse V1, Neoverse-N2, Neoverse-N1, Cortex-X925, Cortex-X4, Cortex-X3, Cortex-X2, Cortex-X1 & X1C, Cortex-A710, Cortex-A78, A78AE & A78C, Cortex-A77, Cortex-A76 & A76A may allow writes to resources owned by a higher exception level.

CVSS v3
9.1
EG Score
9.1(medium)
EPSS
41.6%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 22, 2026

Advisory Details (3)

Auto-updated Jun 9, 2026
No patch confirmed yet.
generic

XSA-493 - Xen Security Advisories

http://xenbits.xen.org/xsa/advisory-493.html
generic

oss-security - Xen Security Advisory 493 v2 (CVE-2025-10263) - Arm: Completion of memory accesses not guaranteed by completion of a TLBI

http://www.openwall.com/lists/oss-security/2026/06/09/13
generic

Documentation – Arm Developer

https://developer.arm.com/documentation/112137

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-rt-0:4.18.0-553.140.1.rt7.481.el8_102026-07-07redhat
redhatkernel-0:4.18.0-553.140.1.el8_102026-07-07redhat
redhatkernel-0:5.14.0-687.22.1.el9_82026-07-06redhat
redhatkernel-0:6.12.0-211.30.1.el10_22026-07-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 218× 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.

Showing the most recent 100 of 340 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-10263?
CVE-2025-10263 is a critical vulnerability published on June 9, 2026. Arm C1-Ultra, C1-Premium, Neoverse V3 & V3AE, Neoverse V2, Neoverse V1, Neoverse-N2, Neoverse-N1, Cortex-X925, Cortex-X4, Cortex-X3, Cortex-X2, Cortex-X1 & X1C, Cortex-A710, Cortex-A78, A78AE & A78C, Cortex-A77, Cortex-A76 & A76A may allow writes to resources owned by a higher exception level.
When was CVE-2025-10263 disclosed?
CVE-2025-10263 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-10263 actively exploited?
CVE-2025-10263 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 41.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-10263?
CVE-2025-10263 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-10263?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-10263, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-10263

Explore →

Is Your Infrastructure Affected by CVE-2025-10263?

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