CVE-2026-65937

HIGHPre-NVD 8.08.0—
EchelonGraph scoreHIGH confidence

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

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

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

In WhatsUp Gold versions released before 2026.0.2, an authenticated attacker can bypass frontend controls and inject persistent script content.

CVSS v3
8.0
EG Score
8.0(high)
EG Risk
36(Track)
EG Risk 36/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
Severity80% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 13, 2026

Advisory Details (3)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

Progress Customer Community

https://community.progress.com/s/article/WhatsUp-Gold-Security-Bulletin-August-2026
generic

WhatsUp Gold 2026.0 Release Notes

https://docs.progress.com/bundle/whatsupgold-release-notes-26-0/page/WhatsUp-Gold-2026.0-Release-Notes.html
generic

WhatsUp Gold Network Monitoring Software | Progress

https://www.progress.com/network-monitoring

Vendor Advisories for CVE-2026-65937(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 / 39× 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-08-20 20:38 UTCGHSA enrichment
  2. 2026-08-20 09:09 UTCGHSA enrichment
  3. 2026-08-19 21:42 UTCEG score recompute
  4. 2026-08-19 21:42 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 10:15 UTCGHSA enrichment
  7. 2026-08-18 22:47 UTCEG score recompute
  8. 2026-08-18 22:47 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 11:18 UTCGHSA enrichment
  11. 2026-08-17 23:51 UTCEG score recompute
  12. 2026-08-17 23:51 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 12:23 UTCGHSA enrichment
  15. 2026-08-17 00:56 UTCEG score recompute
  16. 2026-08-17 00:56 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 13:29 UTCEG score recompute
  19. 2026-08-16 13:29 UTCGHSA enrichment
  20. 2026-08-16 02:02 UTCGHSA enrichment
  21. 2026-08-15 14:35 UTCGHSA enrichment
  22. 2026-08-15 03:08 UTCEG score recompute
  23. 2026-08-15 03:08 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 15:40 UTCGHSA enrichment
Show 14 more
  1. 2026-08-14 04:13 UTCEG score recompute
  2. 2026-08-14 04:13 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 16:46 UTCGHSA enrichment
  5. 2026-08-13 05:19 UTCEG score recompute
  6. 2026-08-13 05:19 UTCGHSA enrichment
  7. 2026-08-13 04:21 UTCEG score recompute
  8. 2026-08-13 04:21 UTCGHSA enrichment
  9. 2026-08-12 18:38 UTCEG score recompute
  10. 2026-08-12 18:38 UTCGHSA enrichment
  11. 2026-08-12 17:26 UTCEG score recompute
  12. 2026-08-12 16:34 UTCEG score recompute
  13. 2026-08-12 15:36 UTCEG score recompute
  14. 2026-08-12 15:35 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-65937?
CVE-2026-65937 is a high vulnerability published on August 12, 2026. In WhatsUp Gold versions released before 2026.0.2, an authenticated attacker can bypass frontend controls and inject persistent script content.
When was CVE-2026-65937 disclosed?
CVE-2026-65937 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65937 actively exploited?
CVE-2026-65937 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 84.3% of all scored CVEs.
What is the CVSS score of CVE-2026-65937?
CVE-2026-65937 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-65937?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65937, 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-65937

Explore →

Is Your Infrastructure Affected by CVE-2026-65937?

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

Start Free Scan →Browse All CVEs