Security readout for executives and security teams
Plain-English summary
Affected HPE AOS-CX network devices may allow an attacker to take control without credentials by sending malicious network packets. Successful exploitation could expose data, alter device operations, or cause outages. The supplied sources do not identify the daemon, affected port, fixed releases, or confirmed exploitation.
Executive priority
Treat as an urgent network-infrastructure remediation because compromise could grant elevated control without credentials. Prioritize externally or broadly reachable devices, but do not claim active attacks from the available evidence. Obtain HPE's current fixed-release guidance and schedule controlled upgrades promptly.
Technical view
Multiple buffer-overflow vulnerabilities in an unspecified AOS-CX daemon improperly process malformed input. The CVSS 3.1 vector indicates network reachability, low attack complexity, no privileges, and no user interaction. Successful exploitation may execute code with elevated privileges, affecting confidentiality, integrity, and availability.
Likely exposure
Potential exposure exists on AOS-CX releases 10.18.0000, 10.17.0000, 10.16.0000, 10.13.0000, and 10.10.0000 when the affected service can receive attacker-controlled packets. The bundle does not specify the daemon, port, default configuration, or whether network segmentation limits reachability.
Exploitation context
The vulnerability is remotely reachable and requires neither authentication nor user interaction according to its CVSS vector. The supplied bundle marks it as absent from KEV and provides no evidence of active exploitation, public proof-of-concept code, or observed attacks.
Researcher notes
The bundle describes multiple buffer overflows but maps CWE-284, an authorization category, without explaining the relationship. It also omits the daemon, protocol, port, crash indicators, affected hardware, fixed versions, and root-cause detail. Safe validation should therefore focus on inventory, reachability, telemetry, and vendor-confirmed remediation rather than active malformed-packet testing.
Mitigation direction
- Inventory AOS-CX devices and compare installed releases with the reported affected versions.
- Review HPE advisory hpesbnw05134en_us for fixed releases and vendor-approved mitigations.
- Apply the vendor-provided fixed release using established network-device change controls.
- Restrict untrusted access to affected devices and services where operationally safe.
- Increase monitoring until every affected or potentially affected device is remediated.
Validation and detection
- Confirm each device model, AOS-CX version, and exposure path in the asset inventory.
- Identify the implicated daemon and port from current HPE guidance before testing reachability.
- Verify installed versions after maintenance against HPE's documented fixed-release guidance.
- Review available network and device telemetry for unusual traffic or crashes affecting the service.
- Reassess segmentation and access controls from each relevant untrusted network zone.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-73749 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9hpeVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05134en_us&docLocale=en_USCVE reference, hpe
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.