LiveActive security incident?Get immediate response
CVE Record

CVE-2025-10263: Arm C1-Ultra, C1-Premium, Neoverse V3 & V3AE, Neoverse V2, Neoverse V1, Neoverse-N2, Neoverse-N1, Cortex-X9...

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A flaw in several Arm processor families may let an attacker alter resources controlled by a more privileged execution level, potentially crossing important security boundaries. Confidentiality and integrity impacts are rated high, while availability impact is not identified. The supplied data does not establish which processor revisions are vulnerable, so organizations need vendor-specific confirmation.

Executive priority

Make this an urgent validation and remediation workstream, especially for multi-tenant or externally reachable infrastructure. The critical score and potential privilege-boundary violation justify rapid action, but the incomplete affected-version data prevents assuming every listed Arm processor is vulnerable. Require asset owners and suppliers to provide applicability and update evidence.

Technical view

CVE-2025-10263 concerns improper privilege handling and a race condition, mapped to CWE-266 and CWE-362. The reported result is writing to resources owned by a higher exception level. Its CVSS 3.1 score is 9.1 (critical), with network-accessible, low-complexity, unauthenticated exploitation asserted by the vector. Exact affected revisions and prerequisites are absent from the bundle.

Likely exposure

Potential exposure spans systems using the listed Arm C1, Neoverse, Cortex-X, and Cortex-A families. However, the normalized affected records specify version “0” and mark products default-unaffected without usable vulnerable ranges. Do not infer exposure from processor family alone; confirm the exact CPU revision, platform firmware, operating system, and vendor advisory status.

Exploitation context

The bundle does not report known active exploitation, and CVE-2025-10263 is not identified as a CISA KEV entry. It also provides no public proof-of-concept or attack prerequisites beyond the CVSS vector. Treat exploitation status as unconfirmed while prioritizing assessment because successful abuse could cross processor exception-level boundaries.

Researcher notes

The supplied record attributes integrity and confidentiality impact without availability impact. CWE-266 suggests incorrect privilege assignment, while CWE-362 indicates concurrent execution involving shared resources. The all-unaffected defaults and version “0” entries are insufficient for revision-level scoping and may reflect incomplete normalization. Researchers should rely on Arm and downstream vendor advisories for conditions, revisions, and remediation details.

Mitigation direction

  • Identify affected hardware and obtain applicability guidance from Arm, system vendors, cloud providers, and operating-system vendors.
  • Apply applicable OEM firmware, Arm guidance, and Red Hat security updates through established change-control processes.
  • Prioritize internet-facing, multi-tenant, virtualization, and other security-boundary-sensitive systems for assessment.
  • Use vendor-recommended compensating controls where updates are unavailable; the supplied sources name no specific workaround.

Validation and detection

  • Inventory exact processor models, revisions, firmware versions, operating systems, hypervisors, and cloud instance types.
  • Compare inventory against Arm document 112137 and applicable platform or operating-system advisories.
  • Verify deployment of relevant firmware and software updates using vendor-supported inventory or compliance tooling.
  • Retest security and virtualization workloads after remediation, including confirmation that required firmware is active.
  • Document systems whose vendors have not yet provided definitive affected-version or remediation guidance.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-266: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-362: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-10263 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
3ADP providers
28Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADP
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N25.8redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2025-10263Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPkernel: Arm Processors: Privilege escalation or information disclosure via writes to higher exception level resources
other:Red Hat severity ratingcvssV3_1
  • 2026-06-09T11:01:37.157Z: Reported to Red Hat.
  • 2026-06-09T09:23:18.802Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ArmC1-Ultra0unaffected
ArmC1-Premium0unaffected
ArmNeoverse V30unaffected
ArmNeoverse V3AE0unaffected
ArmNeoverse V10unaffected
ArmNeoverse N20unaffected
ArmNeoverse N10unaffected
ArmCortex-X9250unaffected
ArmCortex-X40unaffected
ArmCortex-X30unaffected
ArmCortex-X20unaffected
ArmCortex-X10unaffected
ArmCortex-X1C0unaffected
ArmCortex-A7100unaffected
ArmCortex-A780unaffected
ArmCortex-A78AE0unaffected
ArmCortex-A78C0unaffected
ArmCortex-A770unaffected
ArmCortex-A760unaffected
ArmCortex-A76AE0unaffected
Weakness

CWE details

CWE-266CWE-362

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.