CVE-2026-57965

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreHIGH confidence

Score 5.1 from GitHub Security Advisory published 2026-06-29. a secondary CVSS source baseline 5.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.1Exploit: None knownExposed: 0

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

A flaw was found in spice-vdagent. A malicious or compromised SPICE host can trigger an integer overflow by sending a specially crafted message. This vulnerability can lead to a heap buffer overflow, causing the spice-vdagent daemon to crash and resulting in a Denial of Service (DoS) for the virtual machine. This issue requires the SPICE host to be untrusted or compromised for exploitation.

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

Published

June 29, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Jun 29, 2026
Patch available. Sources: redhat.
redhat

2493581 – (CVE-2026-57965) CVE-2026-57965 spice-vdagent: Integer overflow in udscs_write() leading to heap buffer overflow

https://bugzilla.redhat.com/show_bug.cgi?id=2493581
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-57965

Vendor Advisories for CVE-2026-57965(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 16× in last 7d / 61× 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-28 19:54 UTCEG score recompute
  2. 2026-07-28 19:53 UTCGHSA enrichment
  3. 2026-07-28 15:37 UTCEPSS rescore
  4. 2026-07-27 16:58 UTCEG score recompute
  5. 2026-07-27 16:58 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:21 UTCEG score recompute
  9. 2026-07-26 14:21 UTCGHSA enrichment
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-24 14:18 UTCEPSS rescore
  14. 2026-07-23 03:20 UTCEG score recompute
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-22 14:08 UTCEPSS rescore
  17. 2026-07-21 15:25 UTCEPSS rescore
  18. 2026-07-20 17:08 UTCEPSS rescore
  19. 2026-07-19 14:31 UTCEPSS rescore
  20. 2026-07-19 14:31 UTCEPSS rescore
  21. 2026-07-18 10:04 UTCEPSS rescore
  22. 2026-07-17 01:30 UTCGHSA enrichment
  23. 2026-07-16 17:03 UTCEPSS rescore
  24. 2026-07-16 00:33 UTCGHSA enrichment
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 36 more
  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-14 23:35 UTCGHSA enrichment
  3. 2026-07-13 22:31 UTCEPSS rescore
  4. 2026-07-13 22:23 UTCGHSA enrichment
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 21:25 UTCGHSA enrichment
  8. 2026-07-11 20:28 UTCGHSA enrichment
  9. 2026-07-10 19:31 UTCGHSA enrichment
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 18:34 UTCGHSA enrichment
  13. 2026-07-08 17:35 UTCGHSA enrichment
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-07 16:39 UTCGHSA enrichment
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 15:39 UTCGHSA enrichment
  22. 2026-07-05 14:40 UTCGHSA enrichment
  23. 2026-07-05 02:31 UTCEPSS rescore
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-04 13:36 UTCGHSA enrichment
  26. 2026-07-04 06:31 UTCEPSS rescore
  27. 2026-07-04 06:31 UTCEPSS rescore
  28. 2026-07-03 12:39 UTCGHSA enrichment
  29. 2026-07-02 11:40 UTCGHSA enrichment
  30. 2026-07-01 15:07 UTCEPSS rescore
  31. 2026-07-01 10:41 UTCGHSA enrichment
  32. 2026-06-30 23:22 UTCEPSS rescore
  33. 2026-06-30 09:45 UTCGHSA enrichment
  34. 2026-06-29 14:06 UTCEPSS rescore
  35. 2026-06-29 08:48 UTCEG score recompute
  36. 2026-06-29 08:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57965?
CVE-2026-57965 is a medium vulnerability published on June 29, 2026. A flaw was found in spice-vdagent. A malicious or compromised SPICE host can trigger an integer overflow by sending a specially crafted message. This vulnerability can lead to a heap buffer overflow, causing the spice-vdagent daemon to crash and resulting in a Denial of Service (DoS) for the…
When was CVE-2026-57965 disclosed?
CVE-2026-57965 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57965 actively exploited?
CVE-2026-57965 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 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-57965?
CVE-2026-57965 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-57965?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57965, 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-57965

Explore →

Is Your Infrastructure Affected by CVE-2026-57965?

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

Start Free Scan →Browse All CVEs