Skip to main content
VulnerabilityPublished Updated

CVE-2025-64149: Jenkins Publish to Bitbucket Plugin · Cross-Site Request Forgery

Affects Jenkins Publish to Bitbucket PluginSource CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Jenkins Project Jenkins Publish to Bitbucket PluginAffected
  • =0
  • <=0.4
Fixed in–

AI-suggested

  1. Immediately restrict access to Jenkins instances running the Publish to Bitbucket Plugin version 0.4 or earlier by limiting network exposure and enforcing strong authentication and authorization controls.
  2. Monitor Jenkins logs for unusual or unauthorized requests that may indicate exploitation attempts.
  3. Remove or disable the vulnerable plugin until a patched version is released.
  4. Implement web application firewalls (WAFs) or reverse proxies with CSRF protection rules to block suspicious requests targeting Jenkins endpoints.
  5. Enforce the principle of least privilege for Jenkins users and credentials to minimize the impact of compromised credentials.
  6. Regularly audit and rotate credentials stored in Jenkins to reduce the window of opportunity for attackers.
  7. Stay updated with Jenkins security advisories and apply patches promptly once available.
  8. Educate development and DevOps teams about the risks of CSRF and secure plugin usage.

Description

A cross-site request forgery (CSRF) vulnerability in Jenkins Publish to Bitbucket Plugin 0.4 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

References

Community reviews

Loading reviews…