CVE-2013-1050: The default configuration in gnome-screensaver 3.5.4 through 3.6.0 sets the AutostartCondition line to fall...

Security readout for executives and security teams

A GNOME screen locking component could fail to start automatically after login because of a default configuration mistake. On affected systems, an unattended workstation might not lock as expected, allowing someone physically nearby to access the logged-in session. Exposure is most likely on Linux desktops using affected gnome-screensaver versions, especially Ubuntu/GNOME environments from that period. Current exposure depends on installed package versions and whether vendor fixes were applied. Treat this as a workstation hardening issue with moderate urgency. It is not internet-facing, but it can expose active sessions, sensitive data, and internal applications where shared offices, labs, or kiosks rely on automatic locking. Mitigation focus: Apply vendor updates referenced by Ubuntu USN-1716-1 or current distributor guidance.; Replace gnome-screensaver 3.5.4 through 3.6.0 with a fixed package.; Verify the GNOME commit or equivalent downstream fix is present..

Prepared

Jun 24, 2026, 11:46 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.