Filtered by vendor Jenkins
Subscribe
Total
1753 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2026-48917 | 1 Jenkins | 1 Ldap | 2026-06-02 | N/A | 6.6 MEDIUM |
| Jenkins LDAP Plugin 807.v7d7de30930cf and earlier deserializes data from LDAP referrals without validation. | |||||
| CVE-2026-48916 | 1 Jenkins | 1 Ldap | 2026-06-02 | N/A | 6.6 MEDIUM |
| Jenkins LDAP Plugin 807.v7d7de30930cf and earlier follows LDAP referrals. | |||||
| CVE-2026-48926 | 1 Jenkins | 1 Job Import | 2026-06-02 | N/A | 4.3 MEDIUM |
| Jenkins Job Import Plugin 143.v044a_2e819b_27 and earlier does not perform a permission check in an HTTP endpoint, allowing attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins. | |||||
| CVE-2026-48918 | 1 Jenkins | 1 Active Directory | 2026-05-28 | N/A | 6.6 MEDIUM |
| Jenkins Active Directory Plugin 2.41 and earlier follows LDAP referrals by default. | |||||
| CVE-2026-48919 | 1 Jenkins | 1 Active Directory | 2026-05-28 | N/A | 6.6 MEDIUM |
| Jenkins Active Directory Plugin 2.41 and earlier deserializes data from LDAP referrals without validation. | |||||
| CVE-2026-48920 | 1 Jenkins | 1 Email Extension | 2026-05-28 | N/A | 8.8 HIGH |
| Jenkins Email Extension Plugin 1933.v45cec755423f and earlier allows inlining images as `base64` in email content by setting the `data-inline` attribute, without restrictions on the image URLs that can be inlined, allowing attackers able to control the email content to specify `file:` URLs for images to read arbitrary files from the Jenkins controller filesystem. | |||||
| CVE-2026-48921 | 1 Jenkins | 1 Pipeline\ | 2026-05-28 | N/A | 7.5 HIGH |
| Jenkins Pipeline: Groovy Libraries Plugin 797.v90ea_a_9b_e45a_0 and earlier does not prohibit symbolic links in shared libraries, allowing attackers able to control the content of a library used by a Pipeline job to read arbitrary files on the Jenkins controller filesystem. | |||||
| CVE-2026-48922 | 1 Jenkins | 1 Credentials Binding | 2026-05-28 | N/A | 7.5 HIGH |
| Jenkins Credentials Binding Plugin 720.v3f6decef43ea_ and earlier does not properly sanitize file names for file and zip file credentials, allowing attackers able to provide credentials to a job to write files to arbitrary locations on the node filesystem, which can lead to remote code execution if Jenkins is configured to allow a low-privileged user to configure file or zip file credentials used for a job running on the built-in node. | |||||
| CVE-2026-48923 | 1 Jenkins | 1 Appspider | 2026-05-28 | N/A | 4.3 MEDIUM |
| Jenkins AppSpider Plugin 1.0.17 and earlier does not perform a permission check in a method implementing form validation, allowing attackers with Overall/Read permission to connect to an attacker-specified URL. | |||||
| CVE-2026-48924 | 1 Jenkins | 1 Bitbucket Oauth | 2026-05-28 | N/A | 4.3 MEDIUM |
| Jenkins Bitbucket OAuth Plugin 0.17 and earlier does not restrict the redirect URL after login, allowing attackers to perform phishing attacks. | |||||
| CVE-2026-48927 | 1 Jenkins | 1 Buildgraph-view | 2026-05-28 | N/A | 5.5 MEDIUM |
| Jenkins buildgraph-view Plugin 1.8 and earlier does not escape the build URL, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure jobs or views. | |||||
| CVE-2026-9674 | 1 Jenkins | 1 Multijob | 2026-05-28 | N/A | 4.3 MEDIUM |
| A cross-site request forgery (CSRF) vulnerability in Jenkins Multijob Plugin 662.vd2e0001f6b_b_d and earlier allows attackers to resume failed Multijob builds. | |||||
| CVE-2014-9635 | 2 Apache, Jenkins | 2 Tomcat, Jenkins | 2026-05-13 | 5.0 MEDIUM | 5.3 MEDIUM |
| Jenkins before 1.586 does not set the HttpOnly flag in a Set-Cookie header for session cookies when run on Tomcat 7.0.41 or later, which makes it easier for remote attackers to obtain potentially sensitive information via script access to cookies. | |||||
| CVE-2017-1000102 | 1 Jenkins | 1 Static Analysis Utilities | 2026-05-13 | 3.5 LOW | 5.4 MEDIUM |
| The Details view of some Static Analysis Utilities based plugins, was vulnerable to a persisted cross-site scripting vulnerability: Malicious users able to influence the input to these plugins, for example the console output which is parsed to extract build warnings (Warnings Plugin), could insert arbitrary HTML into this view. | |||||
| CVE-2017-1000242 | 1 Jenkins | 1 Git Client | 2026-05-13 | 2.1 LOW | 3.3 LOW |
| Jenkins Git Client Plugin 2.4.2 and earlier creates temporary file with insecure permissions resulting in information disclosure | |||||
| CVE-2017-1000109 | 1 Jenkins | 1 Owasp Dependency-check | 2026-05-13 | 4.3 MEDIUM | 6.1 MEDIUM |
| The custom Details view of the Static Analysis Utilities based OWASP Dependency-Check Plugin, was vulnerable to a persisted cross-site scripting vulnerability: Malicious users able to influence the input to this plugin could insert arbitrary HTML into this view. | |||||
| CVE-2016-4987 | 1 Jenkins | 1 Image Gallery | 2026-05-13 | 4.0 MEDIUM | 6.5 MEDIUM |
| Directory traversal vulnerability in the Image Gallery plugin before 1.4 in Jenkins allows remote attackers to list arbitrary directories and read arbitrary files via unspecified form fields. | |||||
| CVE-2017-1000084 | 1 Jenkins | 1 Parameterized Trigger | 2026-05-13 | 4.0 MEDIUM | 6.5 MEDIUM |
| Parameterized Trigger Plugin fails to check Item/Build permission: The Parameterized Trigger Plugin did not check the build authentication it was running as and allowed triggering any other project in Jenkins. | |||||
| CVE-2017-1000113 | 1 Jenkins | 1 Deploy | 2026-05-13 | 2.1 LOW | 5.5 MEDIUM |
| The Deploy to container Plugin stored passwords unencrypted as part of its configuration. This allowed users with Jenkins master local file system access, or users with Extended Read access to the jobs it is used in, to retrieve those passwords. The Deploy to container Plugin now integrates with Credentials Plugin to store passwords securely, and automatically migrates existing passwords. | |||||
| CVE-2017-1000095 | 1 Jenkins | 1 Script Security | 2026-05-13 | 4.0 MEDIUM | 6.5 MEDIUM |
| The default whitelist included the following unsafe entries: DefaultGroovyMethods.putAt(Object, String, Object); DefaultGroovyMethods.getAt(Object, String). These allowed circumventing many of the access restrictions implemented in the script sandbox by using e.g. currentBuild['rawBuild'] rather than currentBuild.rawBuild. Additionally, the following entries allowed accessing private data that would not be accessible otherwise due to script security: groovy.json.JsonOutput.toJson(Closure); groovy.json.JsonOutput.toJson(Object). | |||||