Technical impact
Jenkins versions prior to 2.587 (and LTS 2.580.1 and earlier) contain a flaw that follows symbolic links when copying the directory of an item that is being renamed. Because of this behavior, an attacker with Item/Create and Item/Configure permissions can craft a symbolic link pointing to any file on the Jenkins controller and then invoke a rename operation. The result is that the attacker can read the contents of that file, giving unauthorized access to sensitive data stored on the controller. This vulnerability delivers information disclosure but does not grant code execution or privilege escalation directly.
Affected Systems
All Jenkins instances running from the Jenkins Project, specifically installations of Jenkins 2.587 or older, as well as the LTS release 2.580.1 and earlier. Any environment where users have Item/Create and Item/Configure permissions is potentially susceptible.
Risk and Exploitability
The EPSS score is less than 1% and the CVSS score of 6.5, and the vulnerability is not currently listed in the CISA KEV catalog, but its impact is significant for environments where the described permissions are granted. The exploit requires only a normal user with the appropriate item manipulation rights and does not rely on additional privileges or remote code execution. Because the attack path is simple – simply rename an item to trigger the symbolic link handling – the practical likelihood of exploitation remains high for compromised or misconfigured accounts.