CVE-2026-7831

HIGHPre-NVD 7.67.6—
EchelonGraph scoreHIGH confidence

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

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

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

UltraVNC viewer through 1.8.2.2 contains an off-by-one stack buffer overflow in the RFB ServerInit message handler. In vncviewer/ClientConnection.cpp, when the server-supplied nameLength equals exactly 2024 the code declares a 2024-byte stack buffer _dn[2024] and calls ReadString(_dn, 2024). ReadString writes the NUL terminator at buf[length], i.e., _dn[2024], one byte past the end of the stack buffer. A malicious VNC server can trigger this condition by advertising a desktop name of length 2024 in its ServerInit message. On release builds without stack canaries the single-byte NUL overwrite adjacent stack data. On builds with /GS stack protection the canary is corrupted and the process terminates, resulting in denial of service. User interaction (connecting the viewer to the malicious server) is required.

CVSS v3
7.6
EG Score
7.6(high)
EPSS
33.5%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 1, 2026
No patch confirmed yet.
generic

Home - UltraVNC VNC OFFICIAL SITE, Remote Desktop Free Opensource

https://uvnc.com/
generic

GitHub - ultravnc/UltraVNC: 👁️ UltraVNC Server, UltraVNC Viewer, UltraVNC Repeater and UltraVNC SC | Official repository: https://github.com/ultravnc/UltraVNC · GitHub

https://github.com/ultravnc/UltraVNC

Vendor Advisories for CVE-2026-7831(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 35× in last 7d / 35× 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-07-06 20:28 UTCEG score recompute
  2. 2026-07-06 20:28 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 09:14 UTCEG score recompute
  6. 2026-07-06 09:13 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 21:58 UTCEG score recompute
  10. 2026-07-05 21:58 UTCGHSA enrichment
  11. 2026-07-05 10:43 UTCEG score recompute
  12. 2026-07-05 10:43 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 23:28 UTCEG score recompute
  16. 2026-07-04 23:28 UTCGHSA enrichment
  17. 2026-07-04 12:14 UTCEG score recompute
  18. 2026-07-04 12:13 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 00:57 UTCEG score recompute
  22. 2026-07-04 00:57 UTCGHSA enrichment
  23. 2026-07-03 13:42 UTCEG score recompute
  24. 2026-07-03 13:42 UTCGHSA enrichment
  25. 2026-07-03 02:27 UTCEG score recompute
Show 10 more
  1. 2026-07-03 02:27 UTCGHSA enrichment
  2. 2026-07-02 15:10 UTCEG score recompute
  3. 2026-07-02 15:10 UTCGHSA enrichment
  4. 2026-07-02 03:51 UTCEG score recompute
  5. 2026-07-02 03:51 UTCGHSA enrichment
  6. 2026-07-01 16:36 UTCEG score recompute
  7. 2026-07-01 16:36 UTCGHSA enrichment
  8. 2026-07-01 15:07 UTCEPSS rescore
  9. 2026-07-01 05:21 UTCEG score recompute
  10. 2026-07-01 05:20 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-7831?
CVE-2026-7831 is a high vulnerability published on July 1, 2026. UltraVNC viewer through 1.8.2.2 contains an off-by-one stack buffer overflow in the RFB ServerInit message handler. In vncviewer/ClientConnection.cpp, when the server-supplied nameLength equals exactly 2024 the code declares a 2024-byte stack buffer dn[2024] and calls ReadString(dn, 2024).…
When was CVE-2026-7831 disclosed?
CVE-2026-7831 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7831 actively exploited?
CVE-2026-7831 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7831?
CVE-2026-7831 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-7831?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7831, 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-7831

Explore →

Is Your Infrastructure Affected by CVE-2026-7831?

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

Start Free Scan →Browse All CVEs