CVE-2025-10263

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

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 (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory

Also known asEUVD-2025-210084 (ENISA EUVD) · GHSA-x9c8-763w-495x (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

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.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
46th
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

June 9, 2026

Last Modified

September 4, 2026

Advisory Details (11)

Auto-updated Sep 15, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.6 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:49031
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support and Red Hat Enterprise Linux 8.4 Extended Update Support

https://access.redhat.com/errata/RHSA-2026:47248
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:40764
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:36349
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:36348
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:36018
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:34911
Web page

XSA-493 - Xen Security Advisories

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

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
Web page

Documentation – Arm Developer

https://developer.arm.com/documentation/112137
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2025-10263

Vendor Advisories for CVE-2025-10263(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fde-lts-26.04 (7.0.0-1013.13) @ resolute2026-11-12ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-11-12ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-11-12ubuntu
ubuntulinux-virtual-6.8 (6.8.0-142.142) @ noble2026-11-12ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1079 (5.15.0-1079.83) @ jammy2026-11-12ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1111.117~20.04.1) @ focal2026-11-12ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.194.171) @ jammy2026-11-12ubuntu
redhatopenshift/ose-rhel-coreos-9:417.94.202608250221-02026-09-03redhat
redhatopenshift/ose-rhel-coreos-9:416.94.202608150307-02026-08-31redhat
redhatopenshift/ose-rhel-coreos-9:415.92.202608180329-02026-08-31redhat
redhatopenshift/ose-rhel-coreos-9:414.92.202608172040-02026-08-31redhat
redhatopenshift/ose-rhel-coreos-9:413.92.202608111330-02026-08-20redhat
redhatopenshift/ose-rhel-coreos-8:412.86.202608080425-02026-08-20redhat
redhatopenshift/ose-rhel-coreos-9:418.94.202608111829-02026-08-19redhat
redhatopenshift/ose-rhel-coreos-9:4.19.9.6.202608120446-02026-08-19redhat
redhatopenshift/ose-rhel-coreos-9:4.20.9.6.202608121719-02026-08-18redhat
redhatopenshift/ose-rhel-coreos-9:4.21.9.6.202608122143-02026-08-18redhat
redhatkernel-0:6.12.0-55.98.1.el10_02026-08-17redhat
redhatkernel-0:4.18.0-477.158.1.el8_82026-08-10redhat
redhatkernel-0:5.14.0-284.186.1.el9_22026-08-07redhat
redhatkernel-0:5.14.0-427.143.1.el9_42026-08-07redhat
redhatkernel-rt-0:5.14.0-284.186.1.rt14.471.el9_22026-08-07redhat
redhatkernel-0:5.14.0-570.131.1.el9_62026-07-31redhat
redhatkernel-0:4.18.0-372.204.1.el8_62026-07-31redhat
redhatkernel-0:4.18.0-305.200.1.el8_42026-07-28redhat
redhatopenshift/ose-rhel-coreos-9:4.22.9.8.202607152026-02026-07-21redhat
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.

Affected Packages

(17 across 9 ecosystems)
Debian:11(3)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
xen4.14.2+25-gb6a8c4f72d-2 ... 4.20.3+127-gc42374a105-1 (46 versions)
  • every version on: no fix on record
—
Debian:12(3)
PackageVulnerable rangeFix by version rangeDependents
arm-trusted-firmware2.10.0+dfsg-1 ... 2.9.0+dfsg-3 (10 versions)
  • every version on: no fix on record
—
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
xen4.17.1+2-gb773c48e36-1 ... 4.17.5+72-g01140da4e8-1 (14 versions)
  • every version up to 4.17.7-0+deb12u1: fixed in 4.17.7-0+deb12u1
—
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
arm-trusted-firmware2.12.1+dfsg-1, 2.12.16+dfsg-1
  • every version on: no fix on record
—
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
xen4.20.0+68-g35cb38b222-1 ... 4.20.2+7-g1badcf5035-2 (6 versions)
  • every version up to 4.20.3+127-gc42374a105-0+deb13u1: fixed in 4.20.3+127-gc42374a105-0+deb13u1
—
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
arm-trusted-firmware2.12.1+dfsg-1
  • every version up to 2.12.16+dfsg-1: fixed in 2.12.16+dfsg-1
—
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (146 versions)
  • every version up to 7.0.13-1: fixed in 7.0.13-1
—
xen4.20.0+68-g35cb38b222-1, 4.20.2+37-g61ff35323e-1, 4.20.2+7-g1badcf5035-1, 4.20.2+7-g1badcf5035-2
  • every version up to 4.20.3+127-gc42374a105-1: fixed in 4.20.3+127-gc42374a105-1
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.18.5-r9: fixed in 4.18.5-r9
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.19.5-r4: fixed in 4.19.5-r4
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.20.3-r4: fixed in 4.20.3-r4
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.20.3-r4: fixed in 4.20.3-r4
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.21.1-r6: fixed in 4.21.1-r6
—

Weakness Classification(2)

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

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 90× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 851 rows 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 751 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-10263?
CVE-2025-10263 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2025-10263 published?
The CVE record for CVE-2025-10263 was published on June 9, 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 September 4, 2026; the record at its source may have been updated since.
Is CVE-2025-10263 actively exploited?
CVE-2025-10263 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2025-10263 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-10263 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs