# Jenkins Aqua Security Scanner Plugin vulnerability exposes scanner tokens

Advisory record · `GHSA-3wgg-3j4j-3f69`

- **Identifiers:** `GHSA-3wgg-3j4j-3f69` · `CVE-2025-53653`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-311](https://cwe.mitre.org/data/definitions/311.html) · [CWE-522](https://cwe.mitre.org/data/definitions/522.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) · [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 9 Jul 2025
- **Updated:** 5 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Jul 2025, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.jenkins-ci.plugins:aqua-security-scanner` (Maven): affected `<=3.2.8`; no fixed version yet

## Machine-written summary

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

> Jenkins Aqua Security Scanner Plugin version 3.2.8 and earlier stores Scanner Tokens for the Aqua API unencrypted in job config.xml files on the Jenkins controller. An attacker with Item/Extended Read permission or access to the controller file system can view these tokens. No fix is listed as of publication.

Written 7 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

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

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

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3wgg-3j4j-3f69)

## Sources

- [GitHub Advisory Database: GHSA-3wgg-3j4j-3f69](https://github.com/advisories/GHSA-3wgg-3j4j-3f69)
- [OSV: GHSA-3wgg-3j4j-3f69](https://osv.dev/vulnerability/GHSA-3wgg-3j4j-3f69)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-53653>
- <https://github.com/jenkinsci/aqua-security-scanner-plugin>
- <https://www.jenkins.io/security/advisory/2025-07-09/#SECURITY-3542>
- <http://www.openwall.com/lists/oss-security/2025/07/09/4>

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-3wgg-3j4j-3f69>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3wgg-3j4j-3f69/>. Everything for agents: <https://agentprime.io/llms.txt>.