# Jenkins does not encrypt secrets from POST config.xml submissions before storing them in job configurations

Advisory record · `GHSA-m6wv-wh8g-64xc`

- **Identifiers:** `GHSA-m6wv-wh8g-64xc` · `BIT-jenkins-2026-53442` · `CVE-2026-53442`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-311](https://cwe.mitre.org/data/definitions/311.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 10 Jun 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Jun 2026, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.jenkins-ci.main:jenkins-core` (Maven): affected `<2.555.3 || >=2.556, <2.568`; fixed in `2.555.3`, `2.568`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Jenkins core versions before 2.555.3, and 2.556 through 2.567, store secrets submitted through POST config.xml requests unencrypted in job config.xml files. Users with Item/Extended Read permission, or anyone with access to the Jenkins controller file system, can read those secrets. Upgrade to 2.555.3 or 2.568, depending on your release line.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0018, the 7th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m6wv-wh8g-64xc)

## Sources

- [GitHub Advisory Database: GHSA-m6wv-wh8g-64xc](https://github.com/advisories/GHSA-m6wv-wh8g-64xc)
- [OSV: GHSA-m6wv-wh8g-64xc](https://osv.dev/vulnerability/GHSA-m6wv-wh8g-64xc)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-53442>
- <https://github.com/jenkinsci/jenkins/commit/037c2c30cd26b926ec9df3d1b60e16b80608edb4>
- <https://github.com/jenkinsci/jenkins/commit/206f0b565f0ce16b5162160ffb96f5dd59002ff7>
- <https://github.com/jenkinsci/jenkins>
- <https://www.jenkins.io/security/advisory/2026-06-10/#SECURITY-3744>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m6wv-wh8g-64xc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m6wv-wh8g-64xc/>. Everything for agents: <https://agentprime.io/llms.txt>.