CyberSecBulletin
CVE-2026-76685NVD status: Analyzed

EdgeConnect SD-WAN Gateways: Integer Overflow or Wraparound

CVE-2026-76685 is a high-severity integer overflow or wraparound vulnerability in EdgeConnect SD-WAN Gateways from Hewlett Packard Enterprise, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected EdgeConnect SD-WAN Gateways versions: 9.7.0.0 and earlier; 9.6.0.0 through 9.6.3.1; 9.5.0.0 through 9.5.8.1, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.67% chance of exploitation within 30 days, higher than 53% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Edgeconnect Sd-wan Orchestrator to 9.4.11 or 9.5.9 or 9.6.4, whichever matches your release line, or a later version.
  2. Update Edgeconnect Operating System to 9.4.9.0 or 9.5.9.0 or 9.6.4.0, whichever matches your release line, or a later version.
  3. Read the advisory on support.hpe.com for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Hewlett Packard EnterpriseEdgeConnect SD-WAN Gateways9.7.0.0 and earlier; 9.6.0.0 through 9.6.3.1; 9.5.0.0 through 9.5.8.1; 9.4.0.0 through 9.4.8.2Not stated
Aruba NetworksEdgeconnect Sd-wan Orchestrator9.4.0 up to, but not including, 9.4.11; 9.5.0 up to, but not including, 9.5.9; 9.6.0 up to, but not including, 9.6.4; 9.7.09.4.11, 9.5.9, 9.6.4
Hewlett Packard EnterpriseEdgeconnect Operating System9.4.0.0 up to, but not including, 9.4.9.0; 9.5.0.0 up to, but not including, 9.5.9.0; 9.6.0.0 up to, but not including, 9.6.4.0; 9.7.0.09.4.9.0, 9.5.9.0, 9.6.4.0

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (hpe.com).

Official description

A vulnerability exists in the proxy packet processing logic of the affected component where it improperly processes malformed or truncated input. An unauthenticated remote attacker could exploit this vulnerability by providing specially crafted input that triggers an integer overflow. Successful exploitation could result in a buffer overflow, potentially leading to remote code execution or denial-of-service.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Integer Overflow or Wraparound

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How developers prevent this class of flaw

  • Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).

More Integer Overflow or Wraparound vulnerabilities (CWE-190)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in EdgeConnect SD-WAN Gateways

All EdgeConnect SD-WAN Gateways vulnerabilities

Recent Integer Overflow or Wraparound vulnerabilities

Spotted an error? Tell us.