RHSA-2026:0077HighCVSS 8.8

Red Hat Security Advisory: spice-client-win security update

Published
January 5, 2026
Last Modified
September 1, 2026

🔗 CVE IDs covered (4)

CVE-2025-59375 →CVE-2025-6965 →CVE-2025-8176 →CVE-2025-9900 →

📋 Description

CVE-2025-6965 — sqlite: Integer Truncation in SQLite CVE-2025-8176 — libtiff: LibTIFF Use-After-Free Vulnerability CVE-2025-9900 — libtiff: Libtiff Write-What-Where CVE-2025-59375 — firefox: thunderbird: expat: libexpat in Expat allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing

🎯 Affected products8

  • Red Hat Enterprise Linux AppStream AUS (v.8.4)
  • Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4)
  • spice-client-win-0:8.10-3.el8_4.1.src as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4)
  • spice-client-win-0:8.10-3.el8_4.1.src as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4)
  • spice-client-win-x64-0:8.10-3.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4)
  • spice-client-win-x64-0:8.10-3.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4)
  • spice-client-win-x86-0:8.10-3.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4)
  • spice-client-win-x86-0:8.10-3.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: To mitigate the issue, limit XML input size and complexity before parsing, and avoid accepting compressed or deeply nested XML. Use OS-level resource controls (like ulimit or setrlimit()) to cap memory usage, or run the parser in a sandboxed or isolated process with strict memory and CPU limits. This helps prevent denial-of-service by containing excessive resource consumption.

🔗 References (7)