CVE-2025-31721: Medium severity jenkins lts vulnerability
A missing permission check in Jenkins 2.503 and earlier, LTS 2.492.2 and earlier allows attackers with Computer/Create permission but without Computer/Configure permission to copy an agent, gaining access to encrypted secrets in its configuration.
Other sources
Jenkins 2.503 and earlier, LTS 2.492.2 and earlier does not perform a permission check in an HTTP endpoint.
This allows attackers with Computer/Create permission but without Computer/Configure permission to copy an agent, gaining access to encrypted secrets in its configuration.
This is due to an incomplete fix of SECURITY-3495/CVE-2025-27622.
Jenkins 2.504, LTS 2.492.3 requires Computer/Configure permission to copy an agent containing secrets.
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-31721?
The severity of CVE-2025-31721 is classified as critical due to the potential unauthorized access to encrypted secrets.
How do I fix CVE-2025-31721?
To fix CVE-2025-31721, update your Jenkins installation to version 2.504 or later, or LTS 2.493 or later.
What are the potential impacts of CVE-2025-31721?
The potential impacts of CVE-2025-31721 include unauthorized access to sensitive data and configuration settings through compromised agents.
Who is affected by CVE-2025-31721?
CVE-2025-31721 affects users of Jenkins versions 2.503 and earlier, as well as LTS versions 2.492.2 and earlier.
What permissions are involved in CVE-2025-31721?
CVE-2025-31721 involves the Computer/Create permission which allows users to copy an agent without the necessary Computer/Configure permission.