# CVE-2025-53659: Jenkins QMetry Test Management Plugin stores unencrypted API keys

> Attackers with extended read permissions or file system access can view unencrypted QMetry API keys stored in Jenkins job configurations.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** No
- **Published:** 9 Jul 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-p9gh-rpjw-78qg

## What is CVE-2025-53659?

CVE-2025-53659 is a medium-severity vulnerability in Jenkins QMetry Test Management Plugin, published on 9 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins QMetry Test Management Plugin 1.13 and earlier stores Qmetry Automation API Keys unencrypted in job config.xml files on the Jenkins controller, where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2025-53659?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:qmetry-test-management` | Maven | All versions to 1.13 | None |
| `org.jenkins-ci.plugins:qmetry-test-management` | Maven | All versions to 1.13 | None |

Products: Jenkins Qmetry Test Management.

## How do I fix CVE-2025-53659?

No fix has been published for CVE-2025-53659 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53659 being exploited?

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

## Other vulnerabilities in Jenkins QMetry Test Management Plugin

- [CVE-2025-53660](https://insights.sbomify.com/CVE-2025-53660/): Jenkins QMetry Test Management Plugin vulnerability exposes API keys (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53659 and fix it if it is affected.

What it is: CVE-2025-53659 is a medium-severity vulnerability in Jenkins QMetry Test Management Plugin, published on 9 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53659 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:qmetry-test-management (Maven): affected all versions up to 1.13; no fix listed
- org.jenkins-ci.plugins:qmetry-test-management (Maven): affected all versions up to 1.13; no fix listed

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-2025-53659/ (Markdown: https://insights.sbomify.com/CVE-2025-53659/index.md)
```

## Sources

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

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