Credential ID disclosure via missing endpoint authorization
Published Aug 5, 2026 · Updated Aug 5, 2026
Missing authorization in Jenkins Violation Comments to GitLab Plugin 2.62.0 and earlier allows remote authenticated users to enumerate credential IDs. An unnamed HTTP endpoint returns IDs for credentials stored in Jenkins without checking the caller's permission to view those credentials. Overall/Read permission is sufficient; the IDs do not expose secret values directly, but they support credential capture when chained with another flaw.
Summary
What happened
Missing authorization in Jenkins Violation Comments to GitLab Plugin 2.62.0 and earlier allows remote authenticated users to enumerate credential IDs. An unnamed HTTP endpoint returns IDs for credentials stored in Jenkins without checking the caller's permission to view those credentials. Overall/Read permission is sufficient; the IDs do not expose secret values directly, but they support credential capture when chained with another flaw.
The record
- CVE
- CVE-2026-70444
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- Jenkins Project
- Product
- Violation Comments to GitLab
- Classifications
- CWE-693
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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 <=2.62.0
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