CyberSecBulletin
CVE-2026-73774NVD status: Analyzed

AOS-CX: Buffer Copy without Checking Size of Input

Published Updated By the CyberSecBulletin desk

CVE-2026-73774 is a high-severity buffer copy without checking size of input vulnerability in AOS-CX from Hewlett Packard Enterprise, with a CVSS 3.1 base score of 7.6 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected AOS-CX versions: 10.18.0000 through 10.18.0001; 10.17.0000 through 10.17.1021; 10.16.0000 through 10.16.1051, 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.29% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of AOS-CX you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on support.hpe.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Hewlett Packard EnterpriseAOS-CX10.18.0000 through 10.18.0001; 10.17.0000 through 10.17.1021; 10.16.0000 through 10.16.1051; 10.13.0000 through 10.13.1180; 10.10.0000 through 10.10.1180Not stated
Hewlett Packard EnterpriseArubaos-cx10.10.1180 and earlier; 10.13.0000 through 10.13.1180; 10.16.0000 through 10.16.1051; 10.17.0000 through 10.17.1021; 10.18.0001Not stated

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
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
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
LowSome restricted data can be read.
Integrity
LowLimited modification of data is possible.
Availability
HighThe component can be taken down completely.

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

Official description

A buffer overflow vulnerability exists in the underlying operating system of AOS-CX that could lead to unauthenticated disclosure of sensitive information by sending specially crafted packets to the affected system. Successful exploitation of this vulnerability could result in limited disclosure or modification of information and disruption of the affected system.

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

The underlying weakness: Buffer Copy without Checking Size of Input

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)

Timeline

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

References

Other vulnerabilities in AOS-CX

All AOS-CX vulnerabilities

Recent Buffer Copy without Checking Size of Input vulnerabilities

Spotted an error? Tell us.