CVE-2021-21697

Agents are allowed some limited access to files on the Jenkins controller file system. The directories agents are allowed to access in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier include the directories storing build-related information, intended to allow agents to store build-related metadata during build execution. As a consequence, this allows any agent to read and write the contents of any build directory stored in Jenkins with very few restrictions (build.xml and some Pipeline-related metadata).

Jenkins 2.319, LTS 2.303.3 prevents agents from accessing contents of build directories unless it’s for builds currently running on the agent attempting to access the directory.

Update Pipeline: Nodes and Processes to version 2.40 or newer for Jenkins to associate Pipeline node blocks with the agent they’re running on for this fix.

If you are unable to immediately upgrade to Jenkins 2.319, LTS 2.303.3, you can install the Remoting Security Workaround Plugin. It will prevent all agent-to-controller file access using FilePath APIs. Because it is more restrictive than Jenkins 2.319, LTS 2.303.3, more plugins are incompatible with it. Make sure to read the plugin documentation before installing it.

CVE-2021-21697 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.319, 2.303.3); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2021-21697? CVE-2021-21697 is a critical-severity security vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions >= 2.304, <= 2.318. It is fixed in 2.319, 2.303.3.
2. How severe is CVE-2021-21697? CVE-2021-21697 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.jenkins-ci.main:jenkins-core are affected by CVE-2021-21697? org.jenkins-ci.main:jenkins-core (maven) versions >= 2.304, <= 2.318 is affected.
4. Is there a fix for CVE-2021-21697? Yes. CVE-2021-21697 is fixed in 2.319, 2.303.3. Upgrade to this version or later.
5. Is CVE-2021-21697 exploitable, and should I be worried? Whether CVE-2021-21697 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2021-21697 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2021-21697?
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.319 or later
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.303.3 or later

Other vulnerabilities in org.jenkins-ci.main:jenkins-core