CVE-2022-29036

CVE-2022-29036 is a medium-severity cross-site scripting (XSS) vulnerability in org.jenkins-ci.plugins:credentials (maven), affecting versions <= 2.6.1. It is fixed in 2.6.1.1, 1074.1076.v39c30cecb_0e2, 1087.1089.v2f1b_9a_b_040e4.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Cross-site Scripting in Jenkins Credentials Plugin

Jenkins Credentials Plugin 1111.v35a_307992395 and earlier, except 1087.1089.v2f1b_9a_b_040e4, 1074.1076.v39c30cecb_0e2, and 2.6.1.1, does not escape the name and description of Credentials parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-29036 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and user interaction required. 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.6.1.1, 1074.1076.v39c30cecb_0e2, 1087.1089.v2f1b_9a_b_040e4); upgrading removes the vulnerable code path.

Affected versions

org.jenkins-ci.plugins:credentials (<= 2.6.1) org.jenkins-ci.plugins:credentials (>= 2.6.2, <= 1074.v60e6c29b) org.jenkins-ci.plugins:credentials (= 1087.v16065d268466) org.jenkins-ci.plugins:credentials (>= 1105, <= 1111.v35a)

Security releases

org.jenkins-ci.plugins:credentials → 2.6.1.1 (maven) org.jenkins-ci.plugins:credentials → 1074.1076.v39c30cecb_0e2 (maven) org.jenkins-ci.plugins:credentials → 1087.1089.v2f1b_9a_b_040e4 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.jenkins-ci.plugins:credentials to 2.6.1.1 or later; org.jenkins-ci.plugins:credentials to 1074.1076.v39c30cecb_0e2 or later; org.jenkins-ci.plugins:credentials to 1087.1089.v2f1b_9a_b_040e4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2022-29036? CVE-2022-29036 is a medium-severity cross-site scripting (XSS) vulnerability in org.jenkins-ci.plugins:credentials (maven), affecting versions <= 2.6.1. It is fixed in 2.6.1.1, 1074.1076.v39c30cecb_0e2, 1087.1089.v2f1b_9a_b_040e4. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
  2. How severe is CVE-2022-29036? CVE-2022-29036 has a CVSS score of 5.4 (Medium). 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.plugins:credentials are affected by CVE-2022-29036? org.jenkins-ci.plugins:credentials (maven) versions <= 2.6.1 is affected.
  4. Is there a fix for CVE-2022-29036? Yes. CVE-2022-29036 is fixed in 2.6.1.1, 1074.1076.v39c30cecb_0e2, 1087.1089.v2f1b_9a_b_040e4. Upgrade to this version or later.
  5. Is CVE-2022-29036 exploitable, and should I be worried? Whether CVE-2022-29036 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-2022-29036 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-2022-29036?
    • Upgrade org.jenkins-ci.plugins:credentials to 2.6.1.1 or later
    • Upgrade org.jenkins-ci.plugins:credentials to 1074.1076.v39c30cecb_0e2 or later
    • Upgrade org.jenkins-ci.plugins:credentials to 1087.1089.v2f1b_9a_b_040e4 or later

Other vulnerabilities in org.jenkins-ci.plugins:credentials

Stop the waste.
Protect your environment with Kodem.