Jenkins Job Configuration History Plugin doesn't redact encrypted values of secrets in job and agent configurations
CVE-2026-57287GHSA-8qr4-27mh-hqfr
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.jenkins-ci.plugins:jobConfigHistory 1367), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.jenkins-ci.plugins:jobConfigHistory
- Affected
- < 1367
- Fixed in
- 1367
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-8qr4-27mh-hqfr lists affected ranges: Maven org.jenkins-ci.plugins:jobConfigHistory >=0 <1367
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-57287: 0.19% estimated exploitation activity in the next 30 days; percentile 9.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Jenkins Job Configuration History Plugin 1356.ve360da6c523a 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.vc8fab15101dc 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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-8qr4-27mh-hqfr
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-57287 Advisory: Jenkins Job Configuration History Plugin doesn't redact encrypted values of secrets in job and agent configurations IDs: CVE-2026-57287, GHSA-8qr4-27mh-hqfr Record: https://patchnext.com/advisories/cve-2026-57287 (revision 1, source checked 26 Oct 2026, 16:55 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins:jobConfigHistory 1367. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.jenkins-ci.plugins:jobConfigHistory: affected < 1367; fixed in 1367 ## Suggested inspection (read-only) - Maven org.jenkins-ci.plugins:jobConfigHistory: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.jenkins-ci.plugins:jobConfigHistory. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-8qr4-27mh-hqfr (GitHub-reviewed advisory GHSA-8qr4-27mh-hqfr lists affected ranges: Maven org.jenkins-ci.plugins:jobConfigHistory >=0 <1367) Commands are suggestions: review each one before running it.
Loading voting…