CVE-2026-63455: Authentication bypass via spoofed HTTP headers Orchestrator REST API
Multiple vulnerabilities in the REST API interface of HPE Networking SD-WAN Orchestrator could allow an unauthenticated remote attacker to bypass web authentication mechanisms and access system functions. Successful exploitation could allow an attacker to view and modify potentially sensitive information on the target system.
Security readout for executives and security teams
Plain-English summary
HPE EdgeConnect SD-WAN Orchestrator builds 9.6.2.00000 and 9.6.3.00000 contain a critical REST API authentication bypass. A remote attacker may spoof HTTP headers to access protected functions without credentials, potentially viewing or changing sensitive information and disrupting the system.
Executive priority
Treat this as an immediate remediation priority because exploitation requires no credentials or user action and may compromise sensitive data and system configuration. First address externally or broadly reachable affected instances, then validate remaining deployments and investigate suspicious activity.
Technical view
The Orchestrator REST API can inadequately enforce authentication when processing spoofed HTTP headers, classified as CWE-306. The CVSS 3.1 score is 9.8: network-accessible, low complexity, no privileges or user interaction required, with potentially high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is highest where an affected Orchestrator REST API is reachable from untrusted networks. The supplied affected list names only versions 9.6.2.00000 and 9.6.3.00000; confirm deployed versions and API accessibility rather than assuming broader impact.
Exploitation context
The sources support unauthenticated remote exploitation potential but provide no evidence of active exploitation. CVE-2026-63455 is not listed as KEV in the supplied bundle. No exploit availability or observed attack activity is established here.
Researcher notes
The bundle identifies spoofed HTTP headers as the bypass vector but does not document the specific headers, affected endpoints, patch versions, or detection indicators. It lists no CPEs and marks unspecified versions unaffected. Consult HPE's bulletin before making broader version or remediation claims.
Mitigation direction
Review the HPE security bulletin for vendor-approved updates or mitigations.
Prioritize affected Orchestrator instances reachable from untrusted networks.
Restrict REST API access to authorized management networks and administrators.
Apply HPE-provided remediation after appropriate testing and change control.
Monitor affected systems for suspicious unauthorized access or configuration changes.
Validation and detection
Inventory EdgeConnect SD-WAN Orchestrator versions across all environments.
Identify systems running 9.6.2.00000 or 9.6.3.00000.
Confirm whether each REST API is reachable from untrusted networks.
Verify vendor remediation status against the HPE security bulletin.
Review access and configuration records for unexplained activity.
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 · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.