Skip to main content
Mallory
CriticalVulnerability

CVE-2026-76673: HPE EdgeConnect SD-WAN Orchestrator API Authentication Bypass

Published Sep 15, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS0.61%50th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Hewlett Packard EnterpriseAruba Networks
IdentifiersCVE-2026-76673CWE-287 · Improper Authentication

CVE-2026-76673 is a critical improper-authentication vulnerability in the API of HPE Aruba Networking EdgeConnect SD-WAN Orchestrator. Crafted API requests can circumvent the Orchestrator's existing authentication controls, allowing a remote unauthenticated actor to obtain administrative privileges without valid credentials. Affected releases include Orchestrator 9.7.0 and earlier, 9.6.3 and earlier, 9.5.8 and earlier, and 9.4.10 and earlier.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation grants administrative access to the EdgeConnect SD-WAN Orchestrator and can result in complete compromise of the Orchestrator host. An attacker with administrative control could access and alter SD-WAN configuration, WAN policies, routing behavior, and managed-gateway configuration, potentially exposing network data and disrupting WAN connectivity.

Mitigation

If you can’t patch tonight, do this now.

Until remediation is complete, restrict CLI, web-management, and API access to trusted administrative networks. Isolate management interfaces on a dedicated Layer 2 segment or VLAN, enforce Layer 3-or-higher firewall policies, and monitor and log administrative activity and anomalous API requests. Investigate potentially exposed systems for prior unauthorized administrative access, as patching does not remove an existing compromise.

Remediation

Patch, then assume compromise.

Upgrade EdgeConnect SD-WAN Orchestrator to the applicable fixed release: 9.7.1 or later, 9.6.4 or later, 9.5.9 or later, or 9.4.11 or later. Ensure the Orchestrator version is equal to or newer than the ECOS version deployed on managed gateways. Systems on unsupported releases should be migrated to a supported fixed version.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Aruba NetworksEdgeconnect Sd-Wan Orchestratorapplication
Hewlett Packard EnterpriseEdgeconnect Operating Systemoperating_system
FAQ

Frequently asked questions

Is CVE-2026-76673 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-76673 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76673?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-76673.
Is there a patch for CVE-2026-76673?
Upgrade EdgeConnect SD-WAN Orchestrator to the applicable fixed release: 9.7.1 or later, 9.6.4 or later, 9.5.9 or later, or 9.4.11 or later. Ensure the Orchestrator version is equal to or newer than the ECOS version deployed on managed gateways.
What products are affected by CVE-2026-76673?
Aruba Networks Edgeconnect Sd-Wan Orchestrator and Hewlett Packard Enterprise Edgeconnect Operating System.
How severe is CVE-2026-76673?
CVE-2026-76673 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.61% (50th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.