CVE-2026-57287

CVE-2026-57287 is a medium-severity security vulnerability in org.jenkins-ci.plugins:jobConfigHistory (maven), affecting versions < 1367. It is fixed in 1367.

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

Jenkins Job Configuration History Plugin doesn't redact encrypted values of secrets in job and agent configurations

Jenkins Job Configuration History Plugin 1356.ve360da_6c523a_ and earlier does not redact the encrypted values of secrets when displaying historical job and agent configurations through its "View as XML" / "(RAW)" feature and its configuration diff views.

This allows attackers with Item/Extended Read permission (but not Item/Configure permission) to view the encrypted values of secrets, such as build trigger tokens, that Jenkins would otherwise redact from the configuration shown to them.

Job Configuration History Plugin 1367.vc8fa_b_15101dc redacts the encrypted values of secrets when displaying historical job and agent configurations through its "View as XML" / "(RAW)" feature and its configuration diff views to users lacking Item/Configure permission.

Impact

CVE-2026-57287 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low 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 (1367); upgrading removes the vulnerable code path.

Affected versions

org.jenkins-ci.plugins:jobConfigHistory (< 1367)

Security releases

org.jenkins-ci.plugins:jobConfigHistory → 1367 (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 org.jenkins-ci.plugins:jobConfigHistory to 1367 or later to resolve this vulnerability.

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

Frequently Asked Questions

  1. What is CVE-2026-57287? CVE-2026-57287 is a medium-severity security vulnerability in org.jenkins-ci.plugins:jobConfigHistory (maven), affecting versions < 1367. It is fixed in 1367.
  2. How severe is CVE-2026-57287? CVE-2026-57287 has a CVSS score of 4.3 (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:jobConfigHistory are affected by CVE-2026-57287? org.jenkins-ci.plugins:jobConfigHistory (maven) versions < 1367 is affected.
  4. Is there a fix for CVE-2026-57287? Yes. CVE-2026-57287 is fixed in 1367. Upgrade to this version or later.
  5. Is CVE-2026-57287 exploitable, and should I be worried? Whether CVE-2026-57287 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-2026-57287 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-2026-57287? Upgrade org.jenkins-ci.plugins:jobConfigHistory to 1367 or later.

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

Stop the waste.
Protect your environment with Kodem.