# CVE-2026-57287: Jenkins Job Configuration History Plugin doesn't redact encrypted values of secrets in job and agent configurations

> Attackers with Extended Read permission can view encrypted secret values in historical configurations due to missing redaction in the Jenkins Job Configuration History Plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-8qr4-27mh-hqfr

## What is CVE-2026-57287?

CVE-2026-57287 is a medium-severity vulnerability in Jenkins Job Configuration History Plugin, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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, allowing attackers with Extended Read permission to view encrypted secret values that would otherwise be redacted.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2026-57287?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:jobConfigHistory. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:jobConfigHistory` | Maven | All versions | 1367 |
| `org.jenkins-ci.plugins:jobConfigHistory` | Maven | All versions | 1367 |

Products: Jenkins Job Configuration History.

## How do I fix CVE-2026-57287?

Upgrade org.jenkins-ci.plugins:jobConfigHistory to 1367 or later.

## Is CVE-2026-57287 being exploited?

There is no known exploitation of CVE-2026-57287 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Job Configuration History Plugin

- [CVE-2023-41933](https://insights.sbomify.com/CVE-2023-41933/): Job Configuration History Plugin's path traversal allows exploiting XXE vulnerability (high 8.8)
- [CVE-2023-41932](https://insights.sbomify.com/CVE-2023-41932/): Path traversal allows exploiting XXE vulnerability in Jenkins Job Configuration History Plugin (medium 6.5)
- [CVE-2023-41931](https://insights.sbomify.com/CVE-2023-41931/): XSS vulnerability in Jenkins Job Configuration History Plugin (medium 5.4)
- [CVE-2022-38664](https://insights.sbomify.com/CVE-2022-38664/): Cross-site Scripting in Jenkins Job Configuration History Plugin (medium 5.4)
- [CVE-2023-41930](https://insights.sbomify.com/CVE-2023-41930/): Path traversal in Jenkins Job Configuration History Plugin (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57287 and fix it if it is affected.

What it is: CVE-2026-57287 is a medium-severity vulnerability in Jenkins Job Configuration History Plugin, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57287 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:jobConfigHistory (Maven): affected all versions; fixed in 1367
- org.jenkins-ci.plugins:jobConfigHistory (Maven): affected all versions; fixed in 1367

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57287/ (Markdown: https://insights.sbomify.com/CVE-2026-57287/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57287
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57287
- OSV: https://osv.dev/vulnerability/CVE-2026-57287

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57287/
Summaries are generated and may contain mistakes; the official description above is the record.