API key disclosure via plaintext job configuration
Published Jul 9, 2025 · Updated Nov 4, 2025
Credential exposure in Jenkins QMetry Test Management Plugin 1.13 and earlier allows remote authenticated users to read Qmetry API keys. The plugin serializes Qmetry Automation API Keys as unencrypted values in each Jenkins job's config.xml file instead of using protected secret storage. Item/Extended Read permission or controller filesystem access is sufficient to recover keys that authorize QMetry automation API actions.
Summary
What happened
Credential exposure in Jenkins QMetry Test Management Plugin 1.13 and earlier allows remote authenticated users to read Qmetry API keys. The plugin serializes Qmetry Automation API Keys as unencrypted values in each Jenkins job's config.xml file instead of using protected secret storage. Item/Extended Read permission or controller filesystem access is sufficient to recover keys that authorize QMetry automation API actions.
The record
- CVE
- CVE-2025-53659
- Published
- Jul 9, 2025
- Updated
- Nov 4, 2025
- Vendor
- Jenkins Project
- Product
- QMetry Test Management Plugin
- Classifications
- CWE-311, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo