CVE-2026-76682

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

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

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

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

A vulnerability in the network security monitoring component of intrusion detection systems could allow an unauthenticated remote attacker to exploit a limited buffer overflow. Successful exploitation could allow an attacker to cause a denial-of-service or potentially execute arbitrary code on the system.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
52(Track)
EG Risk 52/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
Severity82% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 21, 2026

Advisory Details (1)

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

Vendor Advisories for CVE-2026-76682(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 28× in last 7d / 40× 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-25 10:52 UTCGHSA enrichment
  2. 2026-09-24 22:11 UTCEG score recompute
  3. 2026-09-24 22:11 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 09:54 UTCGHSA enrichment
  6. 2026-09-23 21:36 UTCEG score recompute
  7. 2026-09-23 21:36 UTCGHSA enrichment
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-23 09:19 UTCGHSA enrichment
  10. 2026-09-22 21:01 UTCEG score recompute
  11. 2026-09-22 21:01 UTCGHSA enrichment
  12. 2026-09-22 16:01 UTCEPSS rescore
  13. 2026-09-22 08:43 UTCEG score recompute
  14. 2026-09-22 08:43 UTCGHSA enrichment
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-21 20:26 UTCEG score recompute
  17. 2026-09-21 20:26 UTCGHSA enrichment
  18. 2026-09-21 20:00 UTCEG score recompute
  19. 2026-09-21 20:00 UTCGHSA enrichment
  20. 2026-09-21 10:53 UTCGHSA enrichment
  21. 2026-09-20 22:35 UTCGHSA enrichment
  22. 2026-09-20 10:18 UTCGHSA enrichment
  23. 2026-09-19 22:00 UTCEG score recompute
  24. 2026-09-19 22:00 UTCGHSA enrichment
  25. 2026-09-19 09:42 UTCGHSA enrichment
Show 15 more
  1. 2026-09-18 21:15 UTCEG score recompute
  2. 2026-09-18 21:15 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 08:30 UTCGHSA enrichment
  5. 2026-09-17 20:12 UTCEG score recompute
  6. 2026-09-17 20:12 UTCGHSA enrichment
  7. 2026-09-17 07:51 UTCGHSA enrichment
  8. 2026-09-16 19:33 UTCEG score recompute
  9. 2026-09-16 19:33 UTCGHSA enrichment
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 08:58 UTCEG score recompute
  12. 2026-09-16 08:58 UTCGHSA enrichment
  13. 2026-09-15 20:40 UTCEG score recompute
  14. 2026-09-15 19:33 UTCEG score recompute
  15. 2026-09-15 19:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76682?
CVE-2026-76682 is a high vulnerability published on September 15, 2026. A vulnerability in the network security monitoring component of intrusion detection systems could allow an unauthenticated remote attacker to exploit a limited buffer overflow. Successful exploitation could allow an attacker to cause a denial-of-service or potentially execute arbitrary code on the…
When was CVE-2026-76682 disclosed?
CVE-2026-76682 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76682 actively exploited?
CVE-2026-76682 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.3% of all scored CVEs.
What is the CVSS score of CVE-2026-76682?
CVE-2026-76682 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-76682?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76682, 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-76682

Explore →

Is Your Infrastructure Affected by CVE-2026-76682?

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

Book a Demo →Browse All CVEs