Skip to main content
Mallory
CriticalVulnerability

CVE-2026-76672: Authenticated Sensitive Information Disclosure in HPE EdgeConnect SD-WAN Orchestrator

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.9Critical · v3.1
EPSS0.53%45th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Hewlett Packard EnterpriseAruba Networks
IdentifiersCVE-2026-76672CWE-200 · Exposure of Sensitive Information…

CVE-2026-76672 is an authenticated information-disclosure vulnerability in HPE Networking EdgeConnect SD-WAN Orchestrator. A user possessing read-only privileges can submit a specially crafted request to the cache-synchronization endpoint and retrieve sensitive configuration information, including third-party API tokens and credentials. Affected Orchestrator releases include 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.

An attacker with a low-privilege read-only Orchestrator account can obtain credentials and API tokens configured for external services. Those secrets may enable unauthorized access to connected third-party security platforms and facilitate lateral movement beyond the SD-WAN environment.

Mitigation

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

Until upgrades are complete, restrict Orchestrator web and management-interface access to trusted administrative users and networks; isolate management interfaces on a dedicated Layer 2 segment or VLAN and enforce Layer 3-or-higher firewall controls. Apply least privilege to read-only accounts, review their access and activity, and monitor for anomalous cache-synchronization requests or use of connected-service credentials.

Remediation

Patch, then assume compromise.

Upgrade HPE EdgeConnect SD-WAN Orchestrator to 9.7.1 or later, 9.6.4 or later, 9.5.9 or later, or 9.4.11 or later, as applicable. Ensure the Orchestrator release is equal to or newer than the ECOS release running on managed gateways. Rotate third-party API tokens and credentials that may have been accessible to read-only users before remediation.

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-76672 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-76672 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76672?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-76672.
Is there a patch for CVE-2026-76672?
Upgrade HPE EdgeConnect SD-WAN Orchestrator to 9.7.1 or later, 9.6.4 or later, 9.5.9 or later, or 9.4.11 or later, as applicable. Ensure the Orchestrator release is equal to or newer than the ECOS release running on managed gateways.
What products are affected by CVE-2026-76672?
Aruba Networks Edgeconnect Sd-Wan Orchestrator and Hewlett Packard Enterprise Edgeconnect Operating System.
How severe is CVE-2026-76672?
CVE-2026-76672 has a CVSS v3.1 score of 9.9 (Critical) and an EPSS score of 0.53% (45th 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.