CVE-2026-73770

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-09-01. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An authenticated arbitrary file write vulnerability exists in AOS-CX. Successful exploitation could allow an authenticated malicious actor, under specific conditions outside the attacker's control and following a required action by another user, to create or modify arbitrary files and execute arbitrary commands as a privileged user on the underlying operating system.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 4, 2026

Advisory Details (1)

Auto-updated Sep 1, 2026
No patch confirmed yet.
generic
https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05134en_us&docLocale=en_US

Vendor Advisories for CVE-2026-73770(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 71× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 18:32 UTCEG score recompute
  2. 2026-09-19 18:32 UTCGHSA enrichment
  3. 2026-09-19 05:36 UTCEG score recompute
  4. 2026-09-19 05:35 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 16:39 UTCGHSA enrichment
  7. 2026-09-18 03:43 UTCEG score recompute
  8. 2026-09-18 03:43 UTCGHSA enrichment
  9. 2026-09-17 14:47 UTCGHSA enrichment
  10. 2026-09-17 01:51 UTCEG score recompute
  11. 2026-09-17 01:51 UTCGHSA enrichment
  12. 2026-09-16 14:08 UTCEPSS rescore
  13. 2026-09-16 12:54 UTCEG score recompute
  14. 2026-09-16 12:54 UTCGHSA enrichment
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 23:58 UTCGHSA enrichment
  17. 2026-09-15 11:01 UTCEG score recompute
  18. 2026-09-15 11:01 UTCGHSA enrichment
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 21:50 UTCGHSA enrichment
  21. 2026-09-14 08:53 UTCGHSA enrichment
  22. 2026-09-13 19:57 UTCEG score recompute
  23. 2026-09-13 19:57 UTCGHSA enrichment
  24. 2026-09-13 07:01 UTCGHSA enrichment
  25. 2026-09-12 18:05 UTCEG score recompute
Show 46 more
  1. 2026-09-12 18:05 UTCGHSA enrichment
  2. 2026-09-12 15:02 UTCEPSS rescore
  3. 2026-09-12 05:05 UTCGHSA enrichment
  4. 2026-09-11 16:08 UTCEG score recompute
  5. 2026-09-11 16:08 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 03:04 UTCGHSA enrichment
  8. 2026-09-10 14:08 UTCEG score recompute
  9. 2026-09-10 14:08 UTCGHSA enrichment
  10. 2026-09-10 09:35 UTCEPSS rescore
  11. 2026-09-10 01:12 UTCGHSA enrichment
  12. 2026-09-09 12:16 UTCGHSA enrichment
  13. 2026-09-08 23:19 UTCEG score recompute
  14. 2026-09-08 23:19 UTCGHSA enrichment
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-08 10:01 UTCGHSA enrichment
  17. 2026-09-07 20:42 UTCEG score recompute
  18. 2026-09-07 20:42 UTCGHSA enrichment
  19. 2026-09-07 07:45 UTCGHSA enrichment
  20. 2026-09-06 18:46 UTCEG score recompute
  21. 2026-09-06 18:46 UTCGHSA enrichment
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-06 05:49 UTCGHSA enrichment
  24. 2026-09-05 16:53 UTCEG score recompute
  25. 2026-09-05 16:53 UTCGHSA enrichment
  26. 2026-09-05 03:57 UTCGHSA enrichment
  27. 2026-09-04 15:01 UTCEG score recompute
  28. 2026-09-04 15:01 UTCGHSA enrichment
  29. 2026-09-04 05:07 UTCEPSS rescore
  30. 2026-09-04 02:11 UTCGHSA enrichment
  31. 2026-09-03 13:16 UTCEG score recompute
  32. 2026-09-03 13:16 UTCGHSA enrichment
  33. 2026-09-03 04:59 UTCEG score recompute
  34. 2026-09-03 04:59 UTCGHSA enrichment
  35. 2026-09-02 19:39 UTCEG score recompute
  36. 2026-09-02 19:39 UTCGHSA enrichment
  37. 2026-09-02 14:12 UTCEPSS rescore
  38. 2026-09-02 13:34 UTCEG score recompute
  39. 2026-09-02 13:34 UTCGHSA enrichment
  40. 2026-09-02 13:02 UTCEG score recompute
  41. 2026-09-02 13:02 UTCGHSA enrichment
  42. 2026-09-02 10:27 UTCEG score recompute
  43. 2026-09-02 10:26 UTCGHSA enrichment
  44. 2026-09-01 21:26 UTCEG score recompute
  45. 2026-09-01 20:33 UTCEG score recompute
  46. 2026-09-01 20:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73770?
CVE-2026-73770 is a high vulnerability published on September 1, 2026. An authenticated arbitrary file write vulnerability exists in AOS-CX. Successful exploitation could allow an authenticated malicious actor, under specific conditions outside the attacker's control and following a required action by another user, to create or modify arbitrary files and execute…
When was CVE-2026-73770 disclosed?
CVE-2026-73770 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73770 actively exploited?
CVE-2026-73770 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.5% of all scored CVEs.
What is the CVSS score of CVE-2026-73770?
CVE-2026-73770 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-73770?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73770, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73770

Explore →

Is Your Infrastructure Affected by CVE-2026-73770?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs