REDHAT-BUG-2550352: High severity redhat/gnome-remote-desktop vulnerability

Q: Which deployments are exposed to this issue?

RHEL/CentOS deployments using gnome-remote-desktop versions from 0.1.6-1 through 40.0-11 are affected only when the VNC service is enabled and connections use the TLS VNC handler path. Systems without an active VNC listener are not exposed through this path.

Q: What access does an attacker need?

An attacker needs network reachability to the running VNC listener provided by gnome-remote-desktop. Exploitation requires interaction with the TLS VNC connection path; the shipped VNC schema lists tls-anon as the default allowed encryption method.

Q: How can administrators determine whether their system is potentially affected?

Check whether the installed gnome-remote-desktop package version falls within 0.1.6-1 through 40.0-11, then verify that VNC is enabled and reachable. Also determine whether VNC connections can use TLS, since the affected code is limited to the VNC TLS read and write handlers.

Published Oct 13, 2026

Updated

AIONLYREPORT package: gnome-remote-desktop-49.3-1.el10 ------ Summary: Busy-Wait DoS in VNC TLS I/O Handlers (GNUTLSEAGAIN / GNUTLSEINTERRUPTED): retryable TLS read or write results can trap the VNC event-loop thread in an infinite busy loop, causing sustained CPU exhaustion and loss of VNC service availability. Requirements to exploit: An attacker needs network reachability to a running VNC listener provided by gnome-remote-desktop. The issue is configuration-dependent because VNC must be enabled and the connection must exercise the TLS VNC path; the shipped VNC schema uses tls-anon as the default allowed encryption method. Component affected: gnome-remote-desktop, VNC TLS handlers in src/grd-vnc-tls.c (doread() and grdvnctlswritetosocket()), reached from the VNC socket dispatch path in src/grd-session-vnc.c. Version affected: RHEL/CentOS gnome-remote-desktop package versions = 0.1.6-1 through <= 40.0-11 when the VNC service is enabled and the TLS handler path is used (downstream-only). ... Acknowledgement: Aisle Research

Affected Software

1 affected component

redhat/gnome-remote-desktop>=0.1.6-1<=40.0-11

Event History

Oct 13, 2026

Data Sourced

via Red Hat·10:48 AM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which deployments are exposed to this issue?

RHEL/CentOS deployments using gnome-remote-desktop versions from 0.1.6-1 through 40.0-11 are affected only when the VNC service is enabled and connections use the TLS VNC handler path. Systems without an active VNC listener are not exposed through this path.

What access does an attacker need?

An attacker needs network reachability to the running VNC listener provided by gnome-remote-desktop. Exploitation requires interaction with the TLS VNC connection path; the shipped VNC schema lists tls-anon as the default allowed encryption method.

How can administrators determine whether their system is potentially affected?

Check whether the installed gnome-remote-desktop package version falls within 0.1.6-1 through 40.0-11, then verify that VNC is enabled and reachable. Also determine whether VNC connections can use TLS, since the affected code is limited to the VNC TLS read and write handlers.