Credential ID disclosure via unchecked form validation
Published Oct 29, 2025 · Updated Oct 29, 2025
Missing authorization in Jenkins Publish to Bitbucket Plugin 0.4 and earlier allows remote authenticated users to enumerate credential IDs. A form-validation method returns identifiers for credentials stored in Jenkins without checking whether the caller has permission to view them. Overall/Read permission is sufficient; the identifiers do not reveal secret values directly but can support credential capture when chained with another flaw.
Summary
What happened
Missing authorization in Jenkins Publish to Bitbucket Plugin 0.4 and earlier allows remote authenticated users to enumerate credential IDs. A form-validation method returns identifiers for credentials stored in Jenkins without checking whether the caller has permission to view them. Overall/Read permission is sufficient; the identifiers do not reveal secret values directly but can support credential capture when chained with another flaw.
The record
- CVE
- CVE-2025-64148
- Published
- Oct 29, 2025
- Updated
- Oct 29, 2025
- Vendor
- Jenkins Project
- Product
- Publish to Bitbucket
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 29, 2025CVE publishedPublication date reported by the CVE source.
- Oct 29, 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 <=0.4
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