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-105958Spice-server: spice: heap oob read/write via unchecked migration data offsets

Description

A flaw was found in spice-server. Multiple migration data handlers use client-supplied offsets from SPICE_MSGC_MIGRATE_DATA messages without bounds validation, allowing a malicious authenticated SPICE client during VM live migration to read arbitrary heap memory or trigger heap corruption via out-of-bounds read and write operations on the message buffer.

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-105958, 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.25% · top 84% 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 enforce strict bounds validation on client-supplied offsets and buffer lengths across all SPICE migration data handlers prior to memory operations: upgrade to the fixed Spice/Spice Server builds, which validate migration data offsets and read bounds against declared message lengths instead of reallocating from attacker-controlled values, closing all 4 injection vectors (RedCharDevice restore via write_data_ptr offset manipulation, smartcard restore via read_data_ptr offset manipulation, reds agent state restore via msg_header_ptr offset manipulation, DisplayChannelClient migrate data handling via surfaces_at_client_ptr offset manipulation). Until patched, this is a concern on Linux hosts running Spice Server with VM live migration enabled, so disable VM live migration if not required, restrict SPICE client network access using firewall rules, and enforce strong authentication via SASL or mutual TLS. As a compensating measure, randomize heap and binary addresses using ASLR to impede reliable exploitation of out-of-bounds reads and writes, enforce full RELRO and PIE to make Global Offset Table entries read-only and prevent control flow diversion via heap corruption, validate indirect call targets using Control Flow Integrity or shadow call stacks to block redirection upon corruption of function pointers or vtables, enable FORTIFY_SOURCE to detect buffer overflows during memory copy operations such as memcpy and abort execution, and confine the SPICE server process using SELinux in enforcing mode to restrict host access if arbitrary code execution occurs. These controls limit blast radius and contain exploitation, but they do not fix the underlying unchecked migration data offsets defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

References

References2

Sources

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

Badge for a README or a ticket

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

Record last updated .