Jenkins Publish to Bitbucket Plugin is missing a permissions check

published 2025-10-29 12 mo ago modified 2026-10-08 32 d ago also GHSA-v549-7pm5-f8qr , EUVD-2025-36645

cvss: 4.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 19%
public exploits: 0; none known

A missing permission check in Jenkins Publish to Bitbucket Plugin 0.4 and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 12 mo ago (2025-10-29)

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins:publish-to-bitbucket	<=0.4	no fix listed

Affected products

Jenkins Project Jenkins Publish to Bitbucket Plugin

Classification

Weakness

CWE-862 Missing Authorization

References

jenkins.io /security/advisory/2025-10-29/#SECURITY-3570
vendor-advisory, web
openwall.com /lists/oss-security/2025/10/29/2
web
nvd.nist.gov /vuln/detail/CVE-2025-64148
advisory
github.com /jenkinsci/publish-to-bitbucket-plugin
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary