Org.jenkins ci.plugins:publish to bitbucket: Jenkins Publish to Bitbucket Plugin is missing a permissions check
Affects org.jenkins-ci.plugins:publish-to-bitbucketSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium.
Data as of 4 Nov 2026, 18:20 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mavenorg.jenkins-ci.plugins:publish-to-bitbucket | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should monitor the vendor's advisory for updates. Until a fix is released, limit Overall/Read permissions to trusted users only to reduce the risk of credential enumeration.
Description
The Jenkins Publish to Bitbucket Plugin version 0.4 and earlier lacks a permission check in a form validation method. This flaw allows attackers with Overall/Read permission to enumerate credential IDs stored in Jenkins. These credential IDs could potentially be leveraged in conjunction with other vulnerabilities to capture credentials. No fix is currently available for this issue.