Security readout for executives and security teams
Plain-English summary
A high-severity flaw in HPE AOS-CX could let a highly privileged, authenticated attacker access arbitrary files and potentially execute code remotely. Compromise could expose sensitive data, alter switch operations, or disrupt network availability.
Executive priority
Treat as a high-priority credential-dependent infrastructure risk. Accelerate inventory and vendor-guided remediation, particularly for critical network switches or exposed management planes. Although high privileges are required and active exploitation is not evidenced, successful abuse could affect confidentiality, integrity, and availability.
Technical view
CVE-2026-63454 is a CWE-22 path traversal vulnerability reachable over the network by a highly privileged authenticated user. It allows arbitrary files to be copied into a user-readable location through the underlying operating system CLI, potentially enabling remote code execution. CVSS 3.1 is 7.2.
Likely exposure
Exposure is limited to AOS-CX versions 10.13.0000, 10.16.0000, 10.17.0000, and 10.18.0000 according to the supplied record. Exploitation requires authenticated, high-level privileges, reducing initial accessibility but making compromised administrator credentials especially consequential.
Exploitation context
The supplied record does not identify active exploitation, and the CVE is not marked as included in CISA KEV. Exploitation requires high privileges, low complexity, no user interaction, and network access. Public exploit availability is not established by the provided sources.
Researcher notes
The source bundle establishes path traversal, arbitrary file copying, and potential code execution, but does not explain the complete execution chain or name patched versions. Avoid assuming every file disclosure produces code execution. Use the HPE advisory as the authoritative remediation source.
Mitigation direction
- Inventory AOS-CX systems and compare installed versions with the affected version list.
- Review the HPE advisory for fixed releases or vendor-approved mitigations.
- Restrict management interfaces to trusted administrative networks and authorized operators.
- Rotate or disable unnecessary privileged accounts and investigate suspected credential compromise.
- Prioritize vendor remediation for internet-accessible or operationally critical switches.
Validation and detection
- Confirm each device's AOS-CX version using approved asset or management records.
- Verify management interfaces are not unnecessarily exposed to untrusted networks.
- Review privileged account activity for unexpected file access or copying behavior.
- Confirm the installed remediation matches current HPE advisory guidance.
- Reassess affected devices after remediation and document remaining exceptions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-63454 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9hpeVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05081en_us&docLocale=en_USCVE reference, hpe
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.