CVE-2013-4427: pyxtrlock before 0.2 does not properly check the return values of the (1) xcb_grab_pointer and (2) xcb_grab...

Security readout for executives and security teams

CVE-2013-4427 affects pyxtrlock versions before 0.2. The screen lock could fail to fully take control of the keyboard or mouse, so someone physically near the workstation might interact with input devices without unlocking the screen. This is mainly a workstation and shared-terminal risk, not a remote network compromise. Exposure is likely limited to systems using pyxtrlock before 0.2, especially Linux/X11 workstations, shared terminals, labs, kiosks, or unattended desktops where physical access is plausible. Treat this as a targeted physical-access control issue. It deserves prompt remediation on shared or sensitive workstations, but it does not indicate broad internet-facing exposure from the provided evidence. Mitigation focus: Upgrade pyxtrlock to version 0.2 or later where available.; Check operating-system or package-maintainer guidance for fixed builds.; Remove or replace vulnerable pyxtrlock on shared or unattended systems..

Prepared

Jun 14, 2026, 14:16 UTC (UTC+00:00)

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