Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-105959Spice-server: spice: heap buffer overflow via glz dictionary max_encoders integer truncation

Description

A flaw was found in spice-server. The GLZ encoder dictionary restore path truncates a size_t allocation size to int when calling the malloc callback, allowing a malicious authenticated SPICE client during VM live migration to trigger a massive heap buffer overflow by sending a crafted max_encoders value in migration data.

Timeline

  1. ID reserved

    By redhat

  2. · 10 days later

    Published

  3. · 19 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-105959, by who scored it
Scored byCVSSScoreVector
redhatCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Awaiting Analysis3.1High7.5CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.48% · top 58% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

What to do

Workaround: This vulnerability is only exploitable during VM live migration by an authenticated SPICE client. If live migration is not required, disabling it eliminates the attack surface. If live migration is needed, restrict SPICE client connections to trusted networks using firewall rules and enforce strong authentication (TLS with mutual certificate validation, or SASL with strong credentials) to limit who can connect as a SPICE client. --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to prevent integer truncation of size_t allocation calculations to int when invoking the GlzEncoderUsrContext::malloc callback in the GLZ dictionary restore path: upgrade to the fixed Spice/Spice Server builds, which prevent truncation of size_t allocation sizes to int when invoking the GLZ dictionary malloc callback, closing all 2 injection vectors (crafted SPICE_MSGC_MIGRATE_DATA message, malicious max_encoders field in GlzEncDictRestoreData). Until patched, this is a concern on 64-bit Linux hosts running SPICE server, so Disable VM live migration if not required, restrict SPICE client access to trusted networks using firewall rules, and enforce strong authentication via SASL or TLS with mutual certificate validation. As a compensating measure, Run SELinux in enforcing mode to confine the SPICE server process domain and restrict unauthorized system access if the heap overflow is exploited. These controls limit blast radius and contain exploitation, but they do not fix the underlying integer truncation defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-105959 badge
[![CVE-2026-105959](https://cveledger.app/badge/CVE-2026-105959.svg)](https://cveledger.app/cve/CVE-2026-105959)

Record last updated .