RHSA-2026:20576HighCVSS 7.8

Red Hat Security Advisory: tigervnc security update

Published
May 26, 2026
Last Modified
October 2, 2026

🔗 CVE IDs covered (6)

CVE-2026-34001 →CVE-2026-34002 →CVE-2026-34003 →CVE-2026-34352 →CVE-2026-33999 →CVE-2026-34000 →

📋 Description

CVE-2026-33999 — xorg: xwayland: X.Org X server: Denial of Service via integer underflow in XKB compatibility map handling CVE-2026-34000 — xwayland: xorg: X.Org X server: Information disclosure and denial of service via out-of-bounds read in XKB geometry processing. CVE-2026-34001 — xorg: xwayland: X.Org X server: Use-after-free vulnerability leads to server crash and potential memory corruption CVE-2026-34002 — xorg: xwayland: X.Org X server: Information disclosure or Denial of Service via out-of-bounds read in XKB modifier map handling CVE-2026-34003 — xorg: xwayland: X.Org X server: Information exposure and denial of service via out-of-bounds memory access CVE-2026-34352 — TigerVNC: x0vncserver: TigerVNC x0vncserver: Information disclosure, data manipulation, and denial of service via incorrect permissions

🎯 Affected products41

  • Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-0:1.12.0-14.el9_2.14.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-0:1.12.0-14.el9_2.14.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-0:1.12.0-14.el9_2.14.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-0:1.12.0-14.el9_2.14.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-0:1.12.0-14.el9_2.14.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-debuginfo-0:1.12.0-14.el9_2.14.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-debuginfo-0:1.12.0-14.el9_2.14.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-debuginfo-0:1.12.0-14.el9_2.14.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-debuginfo-0:1.12.0-14.el9_2.14.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-debugsource-0:1.12.0-14.el9_2.14.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-debugsource-0:1.12.0-14.el9_2.14.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-debugsource-0:1.12.0-14.el9_2.14.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-debugsource-0:1.12.0-14.el9_2.14.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-icons-0:1.12.0-14.el9_2.14.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-license-0:1.12.0-14.el9_2.14.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-selinux-0:1.12.0-14.el9_2.14.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-0:1.12.0-14.el9_2.14.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-0:1.12.0-14.el9_2.14.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-0:1.12.0-14.el9_2.14.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-0:1.12.0-14.el9_2.14.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-debuginfo-0:1.12.0-14.el9_2.14.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-debuginfo-0:1.12.0-14.el9_2.14.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-debuginfo-0:1.12.0-14.el9_2.14.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-debuginfo-0:1.12.0-14.el9_2.14.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-minimal-0:1.12.0-14.el9_2.14.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-minimal-0:1.12.0-14.el9_2.14.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-minimal-0:1.12.0-14.el9_2.14.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-minimal-0:1.12.0-14.el9_2.14.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • tigervnc-server-minimal-debuginfo-0:1.12.0-14.el9_2.14.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • +11 more not shown

✅ 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: To mitigate this issue, restrict access to the X11 server. For remote access, disable X11 forwarding in SSH configurations if not required. Edit `/etc/ssh/sshd_config` and set `X11Forwarding no`. After modifying the configuration, restart the `sshd` service using `systemctl restart sshd`. Disabling X11 forwarding may impact remote graphical applications. Workaround: To mitigate this vulnerability, restrict access to the X11 server. On systems where a graphical environment is not required, consider disabling the X server entirely by setting the default system target to multi-user mode. For systems requiring the X server, ensure that X11 forwarding is disabled in SSH configurations if not explicitly needed, and restrict direct X11 connections to trusted users and networks through firewall rules. If changes are made to SSH configuration, the `sshd` service must be restarted. If the default system target is changed, a system reboot is required. Workaround: To mitigate this issue, restrict access to the X11 server to trusted users and networks. If the X.Org X server is not required, consider disabling or uninstalling it. For environments where the X server is essential, running X applications within a sandboxed environment can help reduce the attack surface. Workaround: To mitigate this vulnerability, restrict access to the X11 server. If the X.Org X server is not required on a system, consider disabling or uninstalling it. For systems where the X server is necessary, ensure that access is limited to trusted users and networks. This can involve configuring `xhost` or implementing firewall rules to restrict connections to the X server. Any changes to X server configuration or service status may require a restart of the X server for the mitigation to take effect, which will impact active graphical sessions. 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: The x0vncserver component should be disabled if not actively required. If x0vncserver is necessary, ensure that only trusted users have access to the system where it is running. To disable the x0vncserver service, if it is running as a systemd service, you can use: `sudo systemctl stop x0vncserver.service` `sudo systemctl disable x0vncserver.service` If x0vncserver is launched manually, avoid running it in multi-user environments. A service restart or system reboot may be required for changes to take full effect.

🔗 References (9)