Skip to main content
CVE-2025-67639VulnerabilityPublished

CVE-2025-67639: Jenkins · Cross-Site Request Forgery

Affects JenkinsSource CVE Database V5

0

Not known to be exploited · CVSS 3.5 Low.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Dec 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.jenkins-ci/mainpkg:maven/org.jenkins-ci/mainOther threatsAffected
  • <=2.540
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor Jenkins security advisories closely and apply official patches immediately once released. 2. Enable Jenkins’ built-in CSRF protection features if not already active, ensuring that all requests include valid CSRF tokens. 3. Restrict access to Jenkins instances using network segmentation, VPNs, or IP whitelisting to limit exposure to trusted users only. 4. Educate users about the risks of clicking on suspicious links or visiting untrusted websites while logged into Jenkins. 5. Implement multi-factor authentication (MFA) to reduce the risk of session hijacking. 6. Regularly audit Jenkins user sessions and logs for unusual login patterns or unauthorized actions. 7. Consider deploying web application firewalls (WAFs) to detect and block CSRF attack attempts. 8. Use role-based access control (RBAC) to minimize privileges assigned to users and service accounts within Jenkins. 9. Isolate Jenkins environments from critical production systems to contain potential breaches. 10. Conduct penetration testing and vulnerability assessments focused on Jenkins to identify and remediate security gaps.

Description

A cross-site request forgery (CSRF) vulnerability in Jenkins 2.540 and earlier, LTS 2.528.2 and earlier allows attackers to trick users into logging in to the attacker's account.

References

Community reviews

Loading reviews…