CVE-2013-4259: runner/connection_plugins/ssh.py in Ansible before 1.2.3, when using ControlPersist, allows local users to...

Security readout for executives and security teams

Older Ansible versions could create predictable SSH control socket names in /tmp when ControlPersist was enabled. A local user on the Ansible control machine could abuse a symlink to redirect an automation SSH session. This is mainly a risk for legacy, shared, or multi-user automation hosts. Exposure is most likely on Ansible control nodes running versions before 1.2.3 with SSH ControlPersist enabled, especially where untrusted local users can write to /tmp or access the control host. Treat this as a legacy automation-host hygiene issue. It is not sourced as remotely exploitable or actively exploited, but shared Ansible controllers running privileged automation should be remediated promptly because compromise could affect managed infrastructure access. Mitigation focus: Upgrade Ansible to 1.2.3 or later where feasible.; Check current Ansible security guidance before changing production automation behavior.; Disable SSH ControlPersist until upgraded if the vulnerable path is confirmed..

Prepared

Jun 14, 2026, 15:32 UTC (UTC+00:00)

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