Jenkins
Monthly
Path traversal in the Jenkins Robot Framework Plugin (6.2.2 and earlier) allows an authenticated user holding Item/Configure permission to point the plugin's report archive directory at a location outside the build directory, giving attacker-chosen file creation or overwrite anywhere on the Jenkins controller filesystem - an impact that can be escalated to remote code execution. The flaw is remotely reachable (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) and requires no user interaction, but it is gated by the Item/Configure privilege, plugin installation and use, and a build actually executing to trigger the write. No public exploit code has been identified at time of analysis, and the risk concentrates on multi-user or multi-tenant controllers where lower-trust users are permitted to configure jobs.
Stored cross-site scripting in the Jenkins OWASP Dependency-Check Plugin 5.6.4 and earlier allows an authenticated user holding the Item/Configure permission to inject script into the Jenkins UI by way of CWE values that are rendered from Dependency-Check reports without escaping; the payload persists in the stored report and fires only when a victim later loads the affected report page (UI:R), so no unauthenticated or anonymous path exists. No public exploit code has been identified at time of analysis, and the plugin is not listed in CISA KEV, so this is not confirmed actively exploited. Independent assessment rates this as a moderate-priority stored XSS rather than a top-tier emergency despite the 8.0 vendor score, since successful abuse requires a non-trivial job-configuration privilege, depends on a second user viewing the crafted report, and caps out at limited confidentiality and integrity impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).
Stored cross-site scripting in Jenkins Coverage Plugin 3.3358.v9487dde48783 and earlier lets an attacker who already holds Item/Configure permission on a job submit a job configuration through the REST API with a javascript: scheme URL in the unvalidated coverage results ID field, which is then stored and rendered when a victim later opens the job's coverage page. Exploitation therefore requires authenticated low-privilege access (CVSS PR:L) plus victim interaction (UI:R), meaning it is not usable against default unauthenticated Jenkins deployments; Impact on confidentiality, integrity and availability is rated High (CVSS 8.0). No public exploit code or confirmed active exploitation was identified at time of analysis, and CISA's SSVC assessment records Exploitation: none and Automatable: no.
Stored cross-site scripting in Jenkins Warnings Plugin 13.10258.va_17d49a_78c3b_ and earlier lets an authenticated attacker holding Item/Configure permission inject a javascript: scheme value as the analysis results identifier by submitting a job configuration through the REST API, bypassing the validation that the normal UI path performs. The payload is persisted with the job and executes in the browser of any user who later opens the affected Warnings/analysis results page (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, 8.0, CWE-79). No public exploit code has been identified at time of analysis, and CISA SSVC rates exploitation as none and automatable as no, although technical impact is rated total; vendor patches are available in 13.10259.v80f407cb_03a_e and the backport 13.10223.10225.vcf001b_b_b_3a_90.
Sandbox escape in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier allows an authenticated Jenkins user who is permitted to define and run sandboxed scripts - including Pipeline jobs - to break out of the Groovy sandbox and execute arbitrary code on the Jenkins controller. The flaw is a protection-mechanism failure (CWE-693): the sandbox's call-site interception does not cover methods that are added dynamically to a class at runtime, so a crafted script can invoke such a method and run code that should have been blocked. Exploitation requires script-authoring privileges (PR:L) and a deliberately crafted script (AC:H) with no user interaction, giving high confidentiality, integrity, and availability impact on the controller; no public exploit code was identified at the time of analysis, and the practical risk is concentrated in multi-tenant Jenkins deployments where lower-trust users are delegated Pipeline authoring.
Arbitrary code execution in the Jenkins Script Security Plugin (versions up to and including 1415.v9a_f9b_3a_c253d) lets an authenticated attacker who holds permission to define classpath entries run attacker-supplied code inside the Jenkins controller JVM. The plugin downloads the URL-specified JAR twice - it verifies approval against the first response but then loads classpath entries from the second - so an attacker who controls the hosting server can present a benign, approvable JAR on request one and a malicious JAR on request two. The assessed CVSS 3.1 vector (7.5, AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects this time-of-check/time-of-use race: the flaw is remotely reachable but requires an authenticated classpath-defining user and a reliably won race; there is no public exploit code and no confirmed active exploitation identified at time of analysis.
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier: when a user with job-configure privileges defines classpath entries in an item configuration, those entries are silently auto-approved the moment a user holding Overall/Administer permission copies that item or updates its configuration through the REST API or CLI. The result is code execution inside the Jenkins controller JVM (CWE-94, CVSS 8.0), but exploitation is a two-actor, confused-deputy scenario: the attacker needs pre-existing config-edit rights (PR:L) and must wait for a privileged user to perform the copy or API/CLI update (UI:R), so installations where only administrators author jobs and never copy them or drive configuration through REST/CLI are effectively unexposed. No public exploit code or confirmed active exploitation was identified at time of analysis.
Sandbox escape in the Jenkins Script Security Plugin (1415.v9a_f9b_3a_c253d and earlier) allows an authenticated Jenkins user who holds permission to define and run sandboxed scripts - including Pipelines - to execute code outside the Groovy sandbox by supplying an @Builder annotation whose builderStrategy member names an arbitrary class. Exploitation additionally requires that a suitable "gadget" class be present on the classpath of the component that evaluates the script, which is why the assessment rates it AC:H despite high C:H/I:H/A:H impact and a scope change (S:C) across the sandbox boundary; the limitation is that only instances where untrusted or low-privilege users can author sandboxed scripts are meaningfully exposed. No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; EPSS is 0.20% (11th percentile), consistent with a high-severity but precondition-heavy flaw rather than a mass-exploitable internet threat.
Sandbox escape leading to arbitrary code execution inside the Jenkins controller JVM affects Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier because the plugin fails to reject the @GroovyASTTransformationClass annotation in script source. An authenticated Jenkins user with permission to define and run sandboxed scripts, including Pipelines (the CVSS vector carries PR:L), can submit a script that registers a Groovy AST transformation executed at compile time, before the sandbox applies, resulting in high confidentiality, integrity, and availability impact on the controller; our independent assessment scores this 8.8 with a scope change (S:C) rather than the provider's S:U. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, but for any account holding script-submission rights the exploit path is direct rather than theoretical, so the practical risk concentrates on instances that grant Job/Configure or equivalent Pipeline-authoring rights broadly. This is a genuine high-priority vulnerability, not CVSS inflation: the sandbox itself, not a misconfiguration, is the control being bypassed.
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier allows an authenticated attacker with permission to define and run sandboxed Groovy scripts or Pipelines to bypass the sandbox and run code in the Jenkins controller JVM. The flaw is a protection mechanism failure (CWE-693) in how the plugin casts collections, and it carries CVSS 8.8 with PR:L; only users who can author sandboxed scripts or Pipelines can trigger it. No public exploit code was identified at time of analysis, and CISA SSVC rates exploitation as none, but this is high-priority for multi-tenant Jenkins because script-authoring rights are often broadly granted.
Sandbox escape in the Jenkins Script Security Plugin (1415.v9a_f9b_3a_c253d and earlier) allows authenticated users with permission to define and run sandboxed Groovy or Pipeline scripts to execute arbitrary code in the Jenkins controller JVM, because the sandbox fails to intercept method calls, property and attribute accesses, and array accesses made on a null receiver. No non-default configuration is required - the weakness is inherent to the default sandbox - and the flaw is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-693), with CISA SSVC assessing total technical impact but no active exploitation and no public exploit identified at time of analysis. Real-world urgency is moderated by the access prerequisite: the attacker must already hold script-authoring rights, so exposure is concentrated in multi-tenant or delegated Jenkins instances where Pipeline authoring is granted to less-trusted users.
Sandbox escape in the Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier lets an authenticated user who holds permission to define and run sandboxed scripts - including Pipelines - execute arbitrary code in the Jenkins controller JVM, earning a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The root cause is a protection-mechanism failure (CWE-693): the sandbox proxy created when a script coerces a value to a Java interface skips the method check when the coerced value inherits a same-named method, so the interface proxy can be used to reach unchecked code. No public exploit code has been identified at time of analysis and CISA SSVC rates the issue non-automatable (Exploitation: none, Automatable: no, Technical Impact: total), so mass exploitation is not expected; the binding prerequisite is the authenticated script-authoring permission reflected by PR:L, which makes this a real but privilege-gated RCE-class risk.
OS command injection in Jenkins TICS Plugin 2025.1.1 and earlier allows an authenticated, low-privileged Jenkins user who can control build environment variable values to execute arbitrary commands on the build agent hosting the job. The flaw stems from unsanitized environment variable values being passed directly to OS command invocations within the plugin, and the scope change (S:C) means impact falls on the agent node rather than the Jenkins controller. No public exploit code exists and SSVC rates exploitation status as none with non-automatable attack path, placing real-world priority lower than the raw CVSS score suggests.
Stored cross-site scripting in Jenkins Customizable Header Plugin 295.v2544b_ca_19b_97 and earlier allows authenticated attackers with permission to modify plugin appearance settings to inject persistent JavaScript payloads via a crafted SVG icon, executing in the browser context of any Jenkins user who loads the affected header. Because the header renders on every Jenkins page, a single write operation by a low-privileged attacker broadly affects all platform users, including administrators. No public exploit code has been identified at time of analysis, and SSVC categorizes exploitation as none, though technical impact is rated total.
Privilege escalation in Jenkins Microsoft Entra ID Plugin (≤710.v0b_ff8e9cc2d2) allows any Entra tenant member with group-creation rights to inherit Jenkins permissions configured for a privileged group by creating a new Entra group whose display name collides with a privileged group's display name. The plugin incorrectly resolves group identity using both the immutable object ID and the mutable, user-controllable display name, so the collision satisfies the authorization check without the attacker belonging to the legitimate privileged group. No public exploit has been identified and CISA has not listed this in KEV, but exploitation requires only a valid Entra account, making it a meaningful insider or tenant-level escalation path into CI/CD infrastructure.
Arbitrary file write to remote code execution in Jenkins File Parameter Plugin (versions ≤ 425.v3fa_801681b_5e) is achievable by any low-privilege authenticated Jenkins user through a Stapler data binding flaw. By crafting a build request with a path-traversal file parameter, an attacker can write attacker-controlled content to arbitrary locations on the Jenkins controller filesystem, enabling code execution by overwriting Groovy init scripts, SSH authorized_keys, or other sensitive files. No public exploit has been identified at time of analysis, and CISA SSVC rates current exploitation as none - but the technical impact ceiling is total controller compromise.
Unrestricted Java deserialization in Jenkins Performance Plugin 1015.v09ca_52b_3370e and earlier enables any user holding Item/Configure permission to execute arbitrary code on the Jenkins controller. The plugin stores performance test results as serialized Java objects in the build directory and reads them back without enforcing a class allowlist, enabling classic gadget-chain exploitation (CWE-502). No public exploit has been identified at time of analysis, and SSVC rates exploitation as none with non-automatable delivery, but technical impact is rated total - full Jenkins controller compromise.
Path traversal in Jenkins Allure Plugin 2.35.2 and earlier allows any user holding Item/Read permission on a Jenkins job that publishes Allure test reports to read arbitrary files from the Jenkins controller's filesystem, including credentials, configuration files, and secrets stored on the controller. The vulnerability is reachable over the network with only low-level authenticated access - a standard privilege held by most Jenkins users in typical multi-user deployments. No public exploit code has been identified at time of analysis, and CISA SSVC classifies exploitation as none currently, though technical impact is rated total given unconstrained file read on the controller.
Authentication bypass in the Jenkins SAML Plugin (all versions through 4.618.v441a_27fa_46d2) allows any authenticated low-privilege user to overwrite the SAML identity provider metadata file via unrestricted Stapler data binding, replacing it with attacker-controlled content. Once the IdP metadata is replaced, the attacker operates their own SAML authority and can issue assertions claiming any Jenkins user identity - including administrator - granting full platform compromise. No active exploitation is confirmed (not in CISA KEV), and no public POC has been identified at time of analysis.
Path traversal via Stapler data binding in Jenkins ThinBackup Plugin 2.1.4 and earlier allows authenticated low-privileged attackers to overwrite the plugin's backup configuration, redirecting backup output to an attacker-specified directory and injecting arbitrary Jenkins controller filesystem files into backup archives. The primary risk is exfiltration of high-value Jenkins controller secrets - credentials.xml, SSH keys, API tokens, master.key - via the backup mechanism. SSVC rates exploitation as none with no public exploit identified; however, the C:H impact makes this a significant post-initial-access escalation path on CI/CD infrastructure.
Stored cross-site scripting in Jenkins SonarQube Scanner Plugin ≤2.18.3 allows attackers holding Item/Configure permission to inject javascript: scheme URLs into dashboard links the plugin constructs from SonarQube scanner results. The plugin performs no URL-scheme validation, so a malicious javascript: payload persists in the Jenkins UI and executes in any victim's browser that views or interacts with the affected dashboard link. No public exploit or active exploitation has been identified at time of analysis; the Jenkins security team confirmed and published this issue on 2026-09-02.
Session fixation in Jenkins 2.579 and earlier (LTS 2.568.2 and earlier) allows an attacker who can serve content on the same site as Jenkins to inject a known session cookie into a victim's browser; when the victim subsequently authenticates via the persistent 'remember me' cookie without session rotation, the attacker inherits the fully authenticated session. The attack chain requires low-privilege same-site content delivery access and active victim participation in a remember-me login flow, meaningfully constraining real-world exploitability. Vendor patches (Jenkins 2.580 and LTS 2.568.3) are available per the Jenkins Security Advisory published 2026-09-02; no public exploit code or CISA KEV listing exists at time of analysis.
Unsafe Java deserialization in Jenkins 2.579 and earlier (LTS 2.568.2 and earlier) allows authenticated users with configuration-submission permissions to control the values of transient fields during deserialization, with impact ranging up to full server compromise depending on how those fields are used internally. Transient fields in Java are normally excluded from serialization to protect derived or sensitive state; this flaw breaks that guarantee when processing externally supplied configuration data. No public exploit code or active exploitation has been confirmed at time of analysis, but given Jenkins' role as a CI/CD orchestrator with broad network access and secrets, the blast radius of exploitation is significant.
CSRF token leakage in Jenkins allows an attacker who controls any same-origin page on the Jenkins controller to silently steal a valid CSRF crumb from an authenticated user's session and forge privileged requests on their behalf. The vulnerability spans Jenkins 2.447-2.579 (weekly) and LTS 2.452.1-2.568.2 via the bundled Stapler web framework, which embeds the session crumb as a plaintext string literal inside dynamically generated JavaScript responses. No public exploit or CISA KEV listing is present at time of analysis, but successful exploitation yields full account-level action forgery against any authenticated victim who visits the attacker-controlled page.
Stored XSS in Jenkins' system log viewer exposes administrators and privileged users to session hijacking and UI redress attacks, exploitable by any attacker who controls a Jenkins agent process. The vulnerability affects Jenkins 2.579 and earlier (including LTS 2.568.2 and earlier), where log record metadata - source, level, and timestamp - is rendered in the browser without HTML escaping, allowing persistent JavaScript injection via agent-controlled log channels. Patch versions 2.580 (weekly) and LTS 2.568.3 are available per the Jenkins security advisory SECURITY-3967; no public exploit code or CISA KEV listing has been identified at time of analysis.
Unsafe type instantiation during form data binding in Jenkins Stapler allows low-privileged authenticated users to trigger instantiation of arbitrary object types unrelated to the intended field type, achieving full compromise (C:H/I:H/A:H) of the Jenkins controller. Affected are Jenkins 2.579 and earlier and LTS 2.568.2 and earlier, via Stapler 2107.v8dfcb_e8ed317 and earlier (excluding the backport 2088.2093.vd7c3e58008a_6). The root cause is CWE-502-class unsafe deserialization/type-binding: Stapler fails to constrain which Java types may be instantiated when processing attacker-controlled HTTP form submissions. No public exploit code or CISA KEV listing is identified at time of analysis, but Jenkins is pervasively deployed in CI/CD pipelines and the low privilege bar (Overall/Read) makes this a high-priority patch target.
Remote code execution in Jenkins 2.579 and earlier (LTS 2.568.2 and earlier) allows any low-privileged authenticated user to compromise the Jenkins controller by submitting a crafted `config.xml` document. The document embeds objects that Jenkins treats as independent top-level configuration types - such as job definitions or global settings - as nested field values; once bound into Jenkins' runtime object graph, Stapler (Jenkins' HTTP routing framework) begins dispatching live HTTP requests through those embedded objects, providing an attacker-controlled code execution path. Vendor-released patches (Jenkins 2.580, LTS 2.568.3) are available as of 2026-09-02; no KEV listing or public POC is confirmed at time of analysis.
Server-Side Request Forgery in PraisonAI's Jobs API (pip/praisonai < 4.6.58) results from two compounding flaws: a fail-open DNS error handler in `JobSubmitRequest.validate_webhook_url()` that silently accepts any webhook URL when `socket.gaierror` is raised, and a TOCTOU race where `JobExecutor._send_webhook()` performs a completely independent DNS resolution via `httpx.AsyncClient` minutes to hours after validation. Authenticated attackers with a valid API bearer token can submit a job whose `webhook_url` hostname returns NXDOMAIN at validation time, then update DNS to a private IP before job completion, causing the executor to POST job result data to internal infrastructure. A detailed proof-of-concept is publicly available in GHSA-rg5q-pp8p-f7jm; no public exploit identified at time of analysis beyond the PoC, and this CVE is not listed in CISA KEV.
Remote code execution via CSRF in Jenkins Multijob Plugin 669.v9d96a_d9c71b_0 and earlier allows a network attacker to execute arbitrary code within the Jenkins controller JVM by inducing a low-privileged authenticated user to trigger a forged request. The Jenkins security advisory published 2026-08-05 formally discloses this as SECURITY-3823(2), with EUVD-2026-53526 corroborating the affected version range. No public exploit code or CISA KEV listing has been identified at time of analysis, though the network reachability and low attack complexity make this a meaningful risk wherever Jenkins is accessible and users browse untrusted sites within the same browser session.
Remote code execution on the Jenkins controller is achievable by attackers holding Agent/Connect permission via a JEP-200 deserialization filter bypass in the Remoting library (agent.jar/remoting.jar). Jenkins 2.575 and earlier, and LTS 2.568.1 and earlier, include a Remoting version (3384.v60d89463d9e0 and earlier, except the backport 3355.3357.v931d3c992987) that fails to apply the JEP-200 class filter to a fallback deserialization code path, allowing crafted serialized Java objects to reach classes on the Jenkins core classpath that are not blocked by the pre-JEP-200 denylist. No public exploit or CISA KEV listing has been identified at time of analysis, but the primitive - controller-side code execution triggered from an agent - represents a critical trust-boundary violation in Jenkins' controller-agent architecture.
Remote code execution, arbitrary file write, and privilege escalation vulnerabilities in Jenkins core (through 2.575 / LTS 2.568.1) and multiple plugins expose CI/CD infrastructure to full controller compromise. The most critical issue (CVE-2026-70426) allows agent processes and users with Agent/Connect permission to bypass the JEP-200 deserialization class filter via an unguarded fallback path in the Remoting library, enabling code execution on the Jenkins controller. Two independent arbitrary file write vectors (CVE-2026-70427 via malicious tar archives, CVE-2026-70428 via path traversal in file parameter names) can achieve equivalent controller-level code execution by writing Groovy scripts to JENKINS_HOME/init.groovy.d/ or deploying rogue plugins. No CISA KEV listing or public exploit has been identified at time of analysis, though the Jenkins security team coordinated a pre-announcement, suggesting no known active exploitation at disclosure.
Unsandboxed Groovy script execution in Jenkins Multijob Plugin 669.v9d96a_d9c71b_0 and earlier allows any attacker holding Item/Create or Item/Configure permission to run arbitrary code directly on the Jenkins controller JVM. The plugin exposes Groovy scripting capabilities that intentionally bypass the Script Security Plugin - the standard Jenkins mechanism for confining script execution to a restricted sandbox - meaning scripts execute with the full privileges of the Jenkins service account. The fix is available in Multijob Plugin 677.v7ffc23d6a_4c2; no public exploit has been identified at time of analysis and this CVE is not listed in the CISA KEV catalog.
Server-side request forgery and OIDC token forgery in Eclipse CSI PIA lets an unauthenticated attacker abuse a flawed Jenkins issuer allowlist (a bare `startswith('https://ci.eclipse.org')` check in `is_issuer_known`, pia/models.py:139) to redirect OIDC discovery and JWKS fetches to an attacker-controlled host. By posting a crafted issuer such as `https://ci.eclipse.org@evil.host` or `https://ci.eclipse.org.evil.host` to `POST /v1/upload/sbom`, an attacker forces PIA to make outbound requests to arbitrary hosts and to accept a JWT signed with the attacker's own key, effectively bypassing token verification. No public exploit identified at time of analysis, but the flaw is unauthenticated and network-reachable, and the CVSS 3.1 base score is 8.2.
XML external entity (XXE) injection in the Jenkins Assembla Plugin version 1.4 and earlier lets an attacker who can control the HTTP responses of the configured Assembla server read sensitive files and secrets from the Jenkins controller and pivot into internal services via server-side request forgery. Mapped to CWE-918 (SSRF) with a CVSS 3.1 base score of 7.1 (high), there is no public exploit identified at time of analysis and CISA SSVC rates exploitation as 'none' with only partial technical impact. Exploitation requires the attacker to influence what the Assembla endpoint returns, so it is a targeted rather than mass-exploitable condition.
Arbitrary code execution on the Jenkins controller affects the Jenkins OWASP ZAP Plugin version 1.0.7 and earlier, which incorrectly runs build operations on the controller node instead of the designated build agent. An attacker holding Item/Configure permission can leverage this misplaced execution to run arbitrary code in the security context of the controller, escaping agent isolation. No public exploit identified at time of analysis, and CISA SSVC records no known exploitation; EPSS is low at 0.39% (31st percentile).
Path traversal in the Jenkins External Workspace Manager Plugin (versions 1.3.2 and earlier) lets an attacker with Item/Configure permission supply traversal sequences in the custom workspace path of the exwsAllocate Pipeline step to read arbitrary files from the Jenkins controller filesystem, which the vendor notes can escalate to remote code execution. The flaw requires an authenticated low-privileged user (CVSS:3.1 PR:L, base 8.8) and is reported directly by the Jenkins security team. No public exploit identified at time of analysis, and CISA SSVC marks exploitation as none.
Sandbox escape in Jenkins Script Security Plugin 1402.v94c9ce464861 and earlier allows users permitted to run sandboxed Groovy scripts to execute arbitrary code outside the sandbox. The plugin fails to reject Groovy AST transformation annotations that carry an 'extensions' member, so an attacker can point that member at a suitable class already on the evaluating component's classpath and have it run outside sandbox restrictions. No public exploit identified at time of analysis, and SSVC exploitation status is 'none'; EPSS is low at 0.39%.
Sandbox bypass in the Jenkins Script Security Plugin (1402.v94c9ce464861 and earlier) lets users who can supply sandboxed Groovy scripts invoke arbitrary constructors, escaping the sandbox to run unrestricted code on the Jenkins controller. The flaw stems from the plugin failing to intercept implicit type casts on elements of typed for-each loops, a subtle gap in its interception logic. Reported by the Jenkins project (SECURITY-3792) with no public exploit identified at time of analysis; EPSS is low at 0.37% and CISA SSVC records no observed exploitation.
Authenticated remote code execution in Jenkins 2.567 and earlier (LTS 2.555.2 and earlier) allows attackers with permission to submit config.xml to trigger deserialization of arbitrary core or plugin types that subsequently handle HTTP requests, enabling user impersonation, Script Console abuse, and arbitrary file reads from the controller. The flaw is tracked as a CWE-502 unsafe deserialization issue with a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit identified at time of analysis, but the vendor (Jenkins project) has issued a coordinated advisory and patched releases.
Arbitrary file write in the Jenkins Credentials Binding Plugin (version 720.v3f6decef43ea_ and earlier) lets users who can supply file or zip-file credentials to a job write files to attacker-chosen paths on the node filesystem, escalating to remote code execution when Jenkins is configured to let a low-privileged user configure such credentials for a job running on the built-in node. The flaw stems from missing file-name sanitization on the file and zip credential types. Rated CVSS 7.5 with high attack complexity (AC:H); no public exploit identified at time of analysis and the issue is not in CISA KEV.
Arbitrary file read on the Jenkins controller is possible in the Jenkins 'Pipeline: Groovy Libraries Plugin' (version 797.v90ea_a_9b_e45a_0 and earlier), where the plugin fails to prohibit symbolic links inside shared libraries. An attacker who can control the contents of a shared library consumed by a Pipeline job can plant symlinks that resolve to sensitive files (credentials, secrets, configuration) on the controller filesystem and exfiltrate them through the build. There is no public exploit identified at time of analysis, and SSVC marks exploitation status as none, so this is a patch-and-move-on issue rather than an active-exploitation emergency.
Arbitrary file disclosure in the Jenkins Email Extension Plugin (email-ext) versions 1933.v45cec755423f and earlier lets users who can control email content abuse the data-inline image attribute to supply file: URLs, causing the Jenkins controller to read local files and embed their contents as base64 inside outgoing emails. An authenticated attacker with rights to edit job email configuration or templates (CVSS PR:L) can exfiltrate controller secrets, credentials, and configuration. There is no public exploit identified at time of analysis and CISA's SSVC rates exploitation as none, but the CVSS 8.8 score and 'total' technical impact make controller secret theft a serious concern in shared Jenkins environments.
Cookie leakage in curl (libcurl) versions 7.71.0 through 8.19.0 allows remote servers to receive cookies intended for a different host when a stale custom cookie host value persists across requests. The flaw, tracked as CWE-319 (cleartext transmission of sensitive information), carries a CVSS 7.5 and SSVC 'partial' technical impact, with no public exploit identified at time of analysis and an EPSS of 0.01%.
Stored cross-site scripting in Jenkins HTML Publisher Plugin (versions 427 and earlier) lets an attacker with Item/Configure permission inject JavaScript via an unescaped job name and URL written into the legacy wrapper file, which then executes in the browser of any user who later views the published report. There is no public exploit identified at time of analysis and EPSS is very low (0.04%, 12th percentile), but the SSVC technical impact is rated total, meaning a successful payload can fully compromise a victim session such as an administrator's.
Stored cross-site scripting in the Jenkins GitHub Plugin (versions ≤ 1.46.0) lets a low-privileged authenticated user with Overall/Read permission inject JavaScript by controlling the current job URL, which is unsafely embedded into the client-side validation logic for the 'GitHub hook trigger for GITScm polling' feature. When another user — potentially a Jenkins administrator — views the affected page, the attacker's script executes inside their authenticated Jenkins session. No public exploit is identified at time of analysis and EPSS is very low (0.04%), but the CVSS 9.0 rating and scope-changed impact make it a meaningful CI/CD privilege-escalation surface.
Arbitrary file write in the Jenkins Credentials Binding Plugin (version 719.v80e905ef14eb_ and earlier) allows an authenticated user who can supply file or zip file credentials to a job to escape the intended credentials directory via unsanitized file names (path traversal), planting files anywhere on the node filesystem. When Jenkins is configured to let a low-privileged user configure such credentials for a job running on the built-in node, this file write escalates to remote code execution. There is no public exploit identified at time of analysis, and EPSS is low (0.34%, 57th percentile), consistent with the high attack complexity and non-default preconditions.
Path traversal in Allure report generator for Jenkins allows unauthenticated attackers to read arbitrary files from the host system by crafting malicious test result files with specially crafted attachment paths. The vulnerability stems from insufficient path validation when processing attachments during report generation, enabling sensitive files to be included in generated reports. A patch is not currently available.
Jenkins versions 2.442 through 2.554 and LTS 2.426.3 through 2.541.2 contain an origin validation bypass vulnerability in the CLI WebSocket endpoint that allows attackers to conduct DNS rebinding attacks. The vulnerability stems from improper use of Host and X-Forwarded-Host headers to compute expected request origins, enabling attackers to bypass authentication controls and potentially execute arbitrary commands through the CLI WebSocket interface. While no CVSS score, EPSS data, or active exploitation in the wild (KEV) status has been publicly disclosed, the vulnerability affects a critical Jenkins component and was responsibly disclosed by the Jenkins security team.
Jenkins versions 2.554 and earlier (LTS 2.541.2 and earlier) contain a path traversal vulnerability in their handling of tar and tar.gz archive extraction that fails to safely process symbolic links, allowing attackers to write files to arbitrary filesystem locations. Attackers with Item/Configure permission or control over Jenkins agent processes can exploit this to deploy malicious scripts and plugins on the Jenkins controller, achieving code execution with the privileges of the Jenkins process. The vulnerability is particularly concerning because it affects the core Jenkins application and enables privilege escalation through plugin installation mechanisms.
Jenkins versions 2.483-2.550 and LTS 2.492.1-2.541.1 contain a stored XSS vulnerability in the agent offline cause description field that fails to properly sanitize user input. Attackers with Agent/Configure or Agent/Disconnect permissions can inject malicious scripts that execute in the browsers of other users viewing the affected agent configuration. No patch is currently available for this vulnerability.
Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character followed by a file path in an argument with the file's contents,. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resources by rapidly opening and immediately canceling (RST_STREAM) large numbers of streams over a single connection, a technique dubbed the 'Rapid Reset' attack. The flaw is confirmed actively exploited (CISA KEV) following large-scale weaponization observed August through October 2023, with publicly available exploit code and an EPSS score of 94.45% placing it in the 100th percentile for likelihood of exploitation. Virtually every major HTTP/2 stack - including nghttp2, Netty, Envoy, and Eclipse Jetty - is affected.
A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.java that allows attackers able. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.53 and earlier in src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovySandbox.java,. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.50 and earlier in src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SecureGroovyScript.java that allows. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A sandbox bypass vulnerability exists in Pipeline: Declarative Plugin 1.3.3 and earlier in. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.61 and earlier in src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition.java,. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A sandbox bypass vulnerability exists in Script Security Plugin 1.49 and earlier in src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovySandbox.java that allows attackers with the. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A code execution vulnerability exists in the Stapler web framework used by Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in stapler/core/src/main/java/org/kohsuke/stapler/MetaClass.java that. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
The remoting module in Jenkins before 2.32 and LTS before 2.19.3 allows remote attackers to execute arbitrary code via a crafted serialized Java object, which triggers an LDAP query to a third-party. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and EPSS exploitation probability 89.2%.
Multiple unspecified API endpoints in Jenkins before 1.650 and LTS before 1.642.2 allow remote authenticated users to execute arbitrary code via serialized data in an XML file, related to XStream and. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 90.9%.
The Jenkins CLI subsystem in Jenkins before 1.638 and LTS before 1.625.2 allows remote attackers to execute arbitrary code via a crafted serialized Java object, related to a problematic. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and EPSS exploitation probability 90.4%.
The Fingerprints pages in Jenkins before 1.638 and LTS before 1.625.2 might allow remote attackers to obtain sensitive job and build name information via a direct request. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and EPSS exploitation probability 27.4%.
Open redirect in the Jenkins Keycloak Authentication Plugin 2.4.1 and earlier lets an unauthenticated attacker craft a login URL whose post-authentication redirect target is not validated, sending a victim who completes Keycloak login to an arbitrary external site (CWE-601, vendor CVSS 4.3). Only Jenkins instances where this plugin is installed and configured as the active authentication realm are affected, and exploitation requires the victim to click the supplied link and finish authentication (UI:R), so impact is confined to phishing and credential-harvesting rather than direct access to Jenkins. No public exploit code identified at time of analysis and no CISA KEV listing; the primary limiting factors are the mandatory user interaction and the low-integrity impact assessed in the vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N.
Stored cross-site scripting (XSS) in the Jenkins Gitee Plugin (versions up to and including 1301.v8957053c7902) allows an authenticated attacker who can trigger builds via the plugin's push webhook and control the sender name field to inject malicious JavaScript into build causes, which executes when a Jenkins user views the affected build's causes page. The vulnerability requires the plugin's webhook endpoint to be reachable and a user to subsequently view the build page (UI:R). No public exploit code has been identified at time of analysis, and the vendor's CVSS score of 6.8 uses a boilerplate vector; independent assessment rates it as CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N.
Server-side request forgery in the Jenkins Bitbucket Push and Pull Request Plugin (4.0.1 and earlier) lets remote attackers submit a crafted webhook payload whose attacker-controlled URL Jenkins then contacts using the Bitbucket credentials stored in the plugin's configuration, exposing those credentials. Per the vendor CVSS vector (AV:N/AC:L/PR:N/UI:N) the attack is remote, low-complexity, and requires no authentication or user interaction; our independent assessment rates the confidentiality impact as high because successful exploitation yields the stored Bitbucket credential material itself. Exploitation is only possible on Jenkins instances where the plugin is installed, reachable on its webhook trigger endpoint, and actually configured with Bitbucket credentials; no public exploit code has been identified at time of analysis and there is no KEV listing for this CVE.
OAuth flow hijacking in the Jenkins Bitbucket Server Integration Plugin 6.0.1 and earlier allows an attacker to substitute the callback URL used in the plugin's OAuth authorization step and capture the Bitbucket access token issued to a victim. Exploitation is not against a static endpoint: the plugin must be installed with its OAuth authorization flow in active use, the attacker must have an OAuth handshake in progress, and a victim who is already authenticated must complete the authorization step (UI:R) within a timing window the attacker must hit (AC:H). Rated only CVSS 4.2 with no confidentiality or integrity impact beyond the scope of the hijacked victim's token, this is a genuine authentication-flow flaw but a low-priority one; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Credential isolation bypass in Jenkins GitLab Plugin 1.2149.vcfc32c82b_f7f and earlier allows an authenticated user who holds Item/Configure permission on a folder to reach 'alternative GitLab API token credentials' that are scoped to a different folder and that they are not entitled to use, because the plugin caches the GitLab API client under a cache key derived solely from the credentials ID and never incorporates the folder in which the credentials were resolved. Rated CVSS 3.1 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) under CWE-522 (insufficiently protected credentials), the issue is a moderate authorization/credential-isolation flaw rather than an unauthenticated remote compromise, and it only exists on multi-tenant Jenkins controllers that actually rely on folder-scoped credentials - single-tenant installations and controllers where all credentials are global/system-scoped see no practical impact. There is no public exploit identified at time of analysis, CISA SSVC records Exploitation: none and Automatable: no, and the CVE is not KEV-listed, so it warrants scheduled patching rather than emergency response.
Information disclosure in Jenkins Gradle Plugin 2.19.1252.v15196b_5a_6e10 and earlier lets an authenticated Jenkins user who can influence the build log of a Gradle job trick the plugin into fetching build scan data from an attacker-controlled URL in preference to the Develocity server URL set in the plugin's global configuration. Because the plugin attaches the globally configured Develocity access key to that outbound request, the attacker can capture the credential; instances with no Develocity access key configured have nothing to leak, so exposure is conditional rather than universal. No public exploit code has been identified at time of analysis, and this is a genuine but moderate-severity issue: exploitation requires authenticated job-run or job-configure privileges plus a configured access key, and the resulting impact is limited to confidentiality (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
Path traversal in the Jenkins Pipeline: Groovy Libraries Plugin (805.va_fc79344957d and earlier) lets an authenticated user who can configure Pipelines point the `library` step at a path outside the SCM checkout and follow symbolic links, giving read access to files in a resources directory and the ability to delete files in a test directory on the Jenkins controller file system. Exploitation requires the Pipeline-configuration privilege, a symlink placed inside the checkout, and successful traversal during library retrieval, which is reflected in the high attack complexity of the assessed CVSS:3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, base score 4.2). No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), so the practical risk is low-to-moderate and confined to file read and limited file deletion rather than arbitrary write or code execution.
Credential disclosure in Jenkins Pipeline: Multibranch Plugin 841.vec5b_9e1806ec and earlier allows users who already hold Item/Configure permission to capture credentials they are not entitled to by authoring or modifying a Pipeline that invokes the resolveScm step, which fails to establish the correct context for credentials lookup. The issue is an access-control scoping flaw (CWE-863) rated CVSS 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N), reflecting the authenticated Item/Configure prerequisite, the high complexity of targeting specific credential IDs, and impact limited to confidentiality with no integrity or availability effect. It requires a Jenkins instance that actually uses Pipeline/multibranch jobs with resolveScm; at time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified, though the vendor advisory of 2026-09-16 should be reviewed for the fixed release.
Stored cross-site scripting in Jenkins update-center2 3.18.3 and earlier allows an attacker who can submit a plugin for hosting to inject malicious script into plugin download index pages by embedding payloads in plugin names, descriptions, or version metadata. Any user who browses the affected plugin index page triggers the XSS payload in their browser session. No exploitation has been confirmed (SSVC: none, no KEV), and no public exploit code has been identified at time of analysis.
Plaintext token storage in Jenkins Parameterized Remote Trigger Plugin 3.2.2 and earlier exposes authentication tokens to any Jenkins user holding Item/Extended Read permission or to anyone with direct access to the Jenkins controller filesystem. Tokens written to job config.xml files are readable without decryption, potentially allowing lower-privileged users to impersonate legitimate remote-trigger callers and invoke builds on downstream Jenkins instances. No public exploit has been identified; SSVC assessment confirms no active exploitation and a non-automatable attack path.
Missing authorization checks in Jenkins XebiaLabs XL Deploy Plugin 26.1.0 and earlier permit any authenticated Jenkins user holding Overall/Read permission to enumerate the IDs of credentials stored in the Jenkins Credentials store. Although credential values (passwords, tokens, certificates) are not directly exposed, the disclosed identifiers constitute reconnaissance data that could guide follow-on attacks against CI/CD pipeline secrets. No public exploit is identified at time of analysis and SSVC rates exploitation as none with partial technical impact.
Unauthorized configuration overwrite in Jenkins Job Configuration History Plugin (≤1367.vc8fa_b_15101dc) permits any authenticated low-privilege user to redirect the plugin's audit history storage to an attacker-specified filesystem directory and alter history recording settings via unsanitized Stapler data binding. By controlling the storage path, an attacker can corrupt or suppress configuration change audit trails, or potentially access sensitive directory contents at the redirected path. No public exploit code exists and EPSS stands at 0.15% (4th percentile), indicating low real-world exploitation pressure at this time.
Configuration integrity compromise in Jenkins GitLab Plugin 1.9.16 and earlier enables authenticated low-privileged users to overwrite the global GitLab connection URL via Stapler data binding, redirecting GitLab API calls to attacker-controlled infrastructure. This causes Jenkins to transmit administrator-configured GitLab API tokens to the attacker's endpoint whenever a pipeline, webhook, or scheduled job triggers a GitLab API interaction. No KEV listing or public exploit has been identified at time of analysis, but the low privilege bar means any Jenkins account holder can abuse this on unpatched installations.
Cross-site request forgery in Jenkins Pipeline: Groovy Libraries Plugin 798.v5cc688825312 and earlier allows unauthenticated remote attackers to delete shared library caches by tricking an authenticated Jenkins user into visiting a malicious page. The impact affects pipeline integrity and build availability, as deleted caches force library re-fetching and can disrupt CI/CD workflows. No public exploit or KEV status has been identified at time of analysis; the vulnerability was disclosed by Jenkins in its September 2, 2026 security advisory (SECURITY-3815).
Server-side request forgery in Jenkins LDAP Plugin 807.809.vd3a_4e5e4ec98 and earlier allows low-privileged authenticated attackers to cause the Jenkins server to initiate connections to arbitrary, attacker-specified URLs via unsanitized Stapler data binding on the LDAP configuration endpoint. This enables internal network probing or interaction with attacker-controlled infrastructure from the Jenkins server's network perspective. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Unauthorized build cancellation in Jenkins Pipeline: Build Step Plugin 599.v4b_67ea_11b_152 and earlier allows any authenticated low-privilege user to cancel downstream pipeline builds they should not be able to touch. When a pipeline uses the `waitForBuild` step with the `propagateAbort` parameter enabled, aborting the upstream build propagates a cancel signal to downstream jobs without verifying whether the caller holds the required Item/Cancel permission on those downstream jobs. No public exploit has been identified at time of analysis, and EPSS data was not provided in the input.
Missing Item/Cancel permission enforcement in Jenkins Pipeline: Build Step Plugin ≤599.v4b_67ea_11b_152 allows authenticated low-privilege users to cancel downstream builds they are not authorized to abort. When an upstream pipeline job using the `build` step is canceled, the plugin propagates the cancellation to all triggered downstream jobs without verifying that the build's authentication context holds Item/Cancel permission on those downstream jobs. Jenkins reported this in their 2026-09-02 security advisory (SECURITY-3870); no public exploit code has been identified at time of analysis.
Jenkins Script Security Plugin 1412.v7737b_3405f86 and earlier allows any low-privileged authenticated Jenkins user to disable the 'Force the use of the sandbox globally in the system' security control via a missing permission check exposed through Stapler data binding. The CVSS score of 4.3 reflects only the direct act of altering a setting, but the chained real-world risk is substantially higher: disabling global sandbox enforcement removes the primary defense against unrestricted Groovy execution, enabling subsequent RCE by any user with script authorship rights. No public exploit has been identified at time of analysis, and exploitation has not been confirmed by CISA KEV.
Improper use of the @DataBoundConstructor annotation in Jenkins Script Security Plugin versions ≤1412.v7737b_3405f86 enables low-privileged authenticated users to read the plugin's script approval configuration by submitting certain Jenkins forms. The flaw allows enumeration of which Groovy scripts, methods, and signatures have been approved for execution - information that could assist an attacker in mapping permitted scripted operations within the Jenkins environment. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code has been identified at the time of analysis.
Missing authorization in Jenkins' CLI build command allows authenticated low-privileged users to cancel builds they did not initiate. When invoking the `build` CLI command with the `-s` flag (wait-for-completion mode), Jenkins 2.579 and earlier and LTS 2.568.2 and earlier skip the required `Item/Cancel` permission check, enabling any user holding only `Item/Build` permission to abort in-flight builds owned by other users. No public exploit code has been identified at time of analysis, and this issue is not listed in the CISA KEV catalog.
Missing authorization (CWE-862) in Jenkins 2.579 and earlier (LTS 2.568.2 and earlier) permits any authenticated user holding Item/Read on at least one job to read build parameter names and values from jobs they are not authorized to access. The CVSS vector (PR:L, AV:N, AC:L) confirms low-complexity, network-accessible exploitation requiring only a minimal authenticated foothold. Patched releases (2.580 weekly, LTS 2.568.3) are available per the official vendor advisory; no public exploit or CISA KEV listing has been identified at time of analysis.
Jenkins REST API in versions 2.579 and earlier (LTS 2.568.2 and earlier) fails to escape map keys during JSON and Python serialization, enabling authenticated users who can control map property names to inject arbitrary fields into API responses consumed by downstream tooling or users. The flaw (CWE-116, improper output encoding) is rated CVSS 4.3 Medium with integrity-only impact and requires low-privilege authenticated access. No public exploit code or CISA KEV listing has been identified; vendor patches 2.580 and LTS 2.568.3 were released on 2026-09-02.
Static field manipulation in Jenkins' Stapler web framework (SECURITY-3926) allows authenticated users who can submit configuration forms to set public static fields on bound configuration objects, causing changes that propagate globally across the entire Jenkins instance and affect all users and build pipelines. Affected releases are Jenkins 2.579 and earlier (weekly) and LTS 2.568.2 and earlier, with fixed versions 2.580 and LTS 2.568.3 released in the 2026-09-02 security advisory. No public exploit code has been identified and the vulnerability does not appear in CISA KEV, but the global-state impact of successful exploitation exceeds what the per-session CVSS 5.4 score alone suggests.
Improper permission enforcement in Jenkins's Appearance configuration page allows authenticated users holding the Overall/Manage permission to modify Appearance configuration options beyond their authorized scope. Affected are Jenkins 2.579 and earlier (weekly) and LTS 2.568.2 and earlier. The vendor has released fixes in Jenkins 2.580 and LTS 2.568.3; no public exploit or active exploitation has been identified, and EPSS places this at the 6th percentile of exploitation likelihood.
Agent configuration takeover in Jenkins 2.579 and earlier allows an attacker holding Agent/Configure permission on any single agent to overwrite any other agent's configuration by embedding the target agent's name in a crafted XML document submitted to the REST API or CLI update endpoints. Successful exploitation grants the attacker full control of the victim agent's configuration and exposes its inbound agent secret and environment variables - primitives that enable agent impersonation and lateral movement within the CI/CD infrastructure. No public exploit code or CISA KEV listing has been identified at time of analysis; patches are available as Jenkins 2.580 and LTS 2.568.3.
XML deserialization in Jenkins 2.579 and earlier (LTS 2.568.2 and earlier) allows any authenticated user holding the minimal Overall/Read permission to inject crafted XML that causes the server to instantiate user objects as nested field values within other deserialized structures, producing unauthorized modifications to the Jenkins user database. The root cause is CWE-502 - insufficient type filtering during XML deserialization - which permits user-typed objects to be materialized outside normal user-creation workflows. No active exploitation has been confirmed by CISA KEV, and no public exploit code has been identified; patched releases (2.580 weekly, 2.568.3 LTS) are available per the Jenkins security advisory.
CVE-2026-70443 is part of the Jenkins August 5, 2026 batch security advisory covering Jenkins core and multiple plugins. The provided source data does not include the specific vulnerability description for CVE-2026-70443 - the advisory text is truncated before reaching this CVE identifier (described CVEs end around CVE-2026-70435). The full advisory at https://www.jenkins.io/security/advisory/2026-08-05/ contains authoritative details. No active exploitation is confirmed (not listed in CISA KEV), and no EPSS or CVSS data was provided in the source intelligence.
Path traversal in the Jenkins Robot Framework Plugin (6.2.2 and earlier) allows an authenticated user holding Item/Configure permission to point the plugin's report archive directory at a location outside the build directory, giving attacker-chosen file creation or overwrite anywhere on the Jenkins controller filesystem - an impact that can be escalated to remote code execution. The flaw is remotely reachable (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) and requires no user interaction, but it is gated by the Item/Configure privilege, plugin installation and use, and a build actually executing to trigger the write. No public exploit code has been identified at time of analysis, and the risk concentrates on multi-user or multi-tenant controllers where lower-trust users are permitted to configure jobs.
Stored cross-site scripting in the Jenkins OWASP Dependency-Check Plugin 5.6.4 and earlier allows an authenticated user holding the Item/Configure permission to inject script into the Jenkins UI by way of CWE values that are rendered from Dependency-Check reports without escaping; the payload persists in the stored report and fires only when a victim later loads the affected report page (UI:R), so no unauthenticated or anonymous path exists. No public exploit code has been identified at time of analysis, and the plugin is not listed in CISA KEV, so this is not confirmed actively exploited. Independent assessment rates this as a moderate-priority stored XSS rather than a top-tier emergency despite the 8.0 vendor score, since successful abuse requires a non-trivial job-configuration privilege, depends on a second user viewing the crafted report, and caps out at limited confidentiality and integrity impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).
Stored cross-site scripting in Jenkins Coverage Plugin 3.3358.v9487dde48783 and earlier lets an attacker who already holds Item/Configure permission on a job submit a job configuration through the REST API with a javascript: scheme URL in the unvalidated coverage results ID field, which is then stored and rendered when a victim later opens the job's coverage page. Exploitation therefore requires authenticated low-privilege access (CVSS PR:L) plus victim interaction (UI:R), meaning it is not usable against default unauthenticated Jenkins deployments; Impact on confidentiality, integrity and availability is rated High (CVSS 8.0). No public exploit code or confirmed active exploitation was identified at time of analysis, and CISA's SSVC assessment records Exploitation: none and Automatable: no.
Stored cross-site scripting in Jenkins Warnings Plugin 13.10258.va_17d49a_78c3b_ and earlier lets an authenticated attacker holding Item/Configure permission inject a javascript: scheme value as the analysis results identifier by submitting a job configuration through the REST API, bypassing the validation that the normal UI path performs. The payload is persisted with the job and executes in the browser of any user who later opens the affected Warnings/analysis results page (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, 8.0, CWE-79). No public exploit code has been identified at time of analysis, and CISA SSVC rates exploitation as none and automatable as no, although technical impact is rated total; vendor patches are available in 13.10259.v80f407cb_03a_e and the backport 13.10223.10225.vcf001b_b_b_3a_90.
Sandbox escape in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier allows an authenticated Jenkins user who is permitted to define and run sandboxed scripts - including Pipeline jobs - to break out of the Groovy sandbox and execute arbitrary code on the Jenkins controller. The flaw is a protection-mechanism failure (CWE-693): the sandbox's call-site interception does not cover methods that are added dynamically to a class at runtime, so a crafted script can invoke such a method and run code that should have been blocked. Exploitation requires script-authoring privileges (PR:L) and a deliberately crafted script (AC:H) with no user interaction, giving high confidentiality, integrity, and availability impact on the controller; no public exploit code was identified at the time of analysis, and the practical risk is concentrated in multi-tenant Jenkins deployments where lower-trust users are delegated Pipeline authoring.
Arbitrary code execution in the Jenkins Script Security Plugin (versions up to and including 1415.v9a_f9b_3a_c253d) lets an authenticated attacker who holds permission to define classpath entries run attacker-supplied code inside the Jenkins controller JVM. The plugin downloads the URL-specified JAR twice - it verifies approval against the first response but then loads classpath entries from the second - so an attacker who controls the hosting server can present a benign, approvable JAR on request one and a malicious JAR on request two. The assessed CVSS 3.1 vector (7.5, AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects this time-of-check/time-of-use race: the flaw is remotely reachable but requires an authenticated classpath-defining user and a reliably won race; there is no public exploit code and no confirmed active exploitation identified at time of analysis.
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier: when a user with job-configure privileges defines classpath entries in an item configuration, those entries are silently auto-approved the moment a user holding Overall/Administer permission copies that item or updates its configuration through the REST API or CLI. The result is code execution inside the Jenkins controller JVM (CWE-94, CVSS 8.0), but exploitation is a two-actor, confused-deputy scenario: the attacker needs pre-existing config-edit rights (PR:L) and must wait for a privileged user to perform the copy or API/CLI update (UI:R), so installations where only administrators author jobs and never copy them or drive configuration through REST/CLI are effectively unexposed. No public exploit code or confirmed active exploitation was identified at time of analysis.
Sandbox escape in the Jenkins Script Security Plugin (1415.v9a_f9b_3a_c253d and earlier) allows an authenticated Jenkins user who holds permission to define and run sandboxed scripts - including Pipelines - to execute code outside the Groovy sandbox by supplying an @Builder annotation whose builderStrategy member names an arbitrary class. Exploitation additionally requires that a suitable "gadget" class be present on the classpath of the component that evaluates the script, which is why the assessment rates it AC:H despite high C:H/I:H/A:H impact and a scope change (S:C) across the sandbox boundary; the limitation is that only instances where untrusted or low-privilege users can author sandboxed scripts are meaningfully exposed. No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; EPSS is 0.20% (11th percentile), consistent with a high-severity but precondition-heavy flaw rather than a mass-exploitable internet threat.
Sandbox escape leading to arbitrary code execution inside the Jenkins controller JVM affects Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier because the plugin fails to reject the @GroovyASTTransformationClass annotation in script source. An authenticated Jenkins user with permission to define and run sandboxed scripts, including Pipelines (the CVSS vector carries PR:L), can submit a script that registers a Groovy AST transformation executed at compile time, before the sandbox applies, resulting in high confidentiality, integrity, and availability impact on the controller; our independent assessment scores this 8.8 with a scope change (S:C) rather than the provider's S:U. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, but for any account holding script-submission rights the exploit path is direct rather than theoretical, so the practical risk concentrates on instances that grant Job/Configure or equivalent Pipeline-authoring rights broadly. This is a genuine high-priority vulnerability, not CVSS inflation: the sandbox itself, not a misconfiguration, is the control being bypassed.
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier allows an authenticated attacker with permission to define and run sandboxed Groovy scripts or Pipelines to bypass the sandbox and run code in the Jenkins controller JVM. The flaw is a protection mechanism failure (CWE-693) in how the plugin casts collections, and it carries CVSS 8.8 with PR:L; only users who can author sandboxed scripts or Pipelines can trigger it. No public exploit code was identified at time of analysis, and CISA SSVC rates exploitation as none, but this is high-priority for multi-tenant Jenkins because script-authoring rights are often broadly granted.
Sandbox escape in the Jenkins Script Security Plugin (1415.v9a_f9b_3a_c253d and earlier) allows authenticated users with permission to define and run sandboxed Groovy or Pipeline scripts to execute arbitrary code in the Jenkins controller JVM, because the sandbox fails to intercept method calls, property and attribute accesses, and array accesses made on a null receiver. No non-default configuration is required - the weakness is inherent to the default sandbox - and the flaw is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-693), with CISA SSVC assessing total technical impact but no active exploitation and no public exploit identified at time of analysis. Real-world urgency is moderated by the access prerequisite: the attacker must already hold script-authoring rights, so exposure is concentrated in multi-tenant or delegated Jenkins instances where Pipeline authoring is granted to less-trusted users.
Sandbox escape in the Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier lets an authenticated user who holds permission to define and run sandboxed scripts - including Pipelines - execute arbitrary code in the Jenkins controller JVM, earning a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The root cause is a protection-mechanism failure (CWE-693): the sandbox proxy created when a script coerces a value to a Java interface skips the method check when the coerced value inherits a same-named method, so the interface proxy can be used to reach unchecked code. No public exploit code has been identified at time of analysis and CISA SSVC rates the issue non-automatable (Exploitation: none, Automatable: no, Technical Impact: total), so mass exploitation is not expected; the binding prerequisite is the authenticated script-authoring permission reflected by PR:L, which makes this a real but privilege-gated RCE-class risk.
OS command injection in Jenkins TICS Plugin 2025.1.1 and earlier allows an authenticated, low-privileged Jenkins user who can control build environment variable values to execute arbitrary commands on the build agent hosting the job. The flaw stems from unsanitized environment variable values being passed directly to OS command invocations within the plugin, and the scope change (S:C) means impact falls on the agent node rather than the Jenkins controller. No public exploit code exists and SSVC rates exploitation status as none with non-automatable attack path, placing real-world priority lower than the raw CVSS score suggests.
Stored cross-site scripting in Jenkins Customizable Header Plugin 295.v2544b_ca_19b_97 and earlier allows authenticated attackers with permission to modify plugin appearance settings to inject persistent JavaScript payloads via a crafted SVG icon, executing in the browser context of any Jenkins user who loads the affected header. Because the header renders on every Jenkins page, a single write operation by a low-privileged attacker broadly affects all platform users, including administrators. No public exploit code has been identified at time of analysis, and SSVC categorizes exploitation as none, though technical impact is rated total.
Privilege escalation in Jenkins Microsoft Entra ID Plugin (≤710.v0b_ff8e9cc2d2) allows any Entra tenant member with group-creation rights to inherit Jenkins permissions configured for a privileged group by creating a new Entra group whose display name collides with a privileged group's display name. The plugin incorrectly resolves group identity using both the immutable object ID and the mutable, user-controllable display name, so the collision satisfies the authorization check without the attacker belonging to the legitimate privileged group. No public exploit has been identified and CISA has not listed this in KEV, but exploitation requires only a valid Entra account, making it a meaningful insider or tenant-level escalation path into CI/CD infrastructure.
Arbitrary file write to remote code execution in Jenkins File Parameter Plugin (versions ≤ 425.v3fa_801681b_5e) is achievable by any low-privilege authenticated Jenkins user through a Stapler data binding flaw. By crafting a build request with a path-traversal file parameter, an attacker can write attacker-controlled content to arbitrary locations on the Jenkins controller filesystem, enabling code execution by overwriting Groovy init scripts, SSH authorized_keys, or other sensitive files. No public exploit has been identified at time of analysis, and CISA SSVC rates current exploitation as none - but the technical impact ceiling is total controller compromise.
Unrestricted Java deserialization in Jenkins Performance Plugin 1015.v09ca_52b_3370e and earlier enables any user holding Item/Configure permission to execute arbitrary code on the Jenkins controller. The plugin stores performance test results as serialized Java objects in the build directory and reads them back without enforcing a class allowlist, enabling classic gadget-chain exploitation (CWE-502). No public exploit has been identified at time of analysis, and SSVC rates exploitation as none with non-automatable delivery, but technical impact is rated total - full Jenkins controller compromise.
Path traversal in Jenkins Allure Plugin 2.35.2 and earlier allows any user holding Item/Read permission on a Jenkins job that publishes Allure test reports to read arbitrary files from the Jenkins controller's filesystem, including credentials, configuration files, and secrets stored on the controller. The vulnerability is reachable over the network with only low-level authenticated access - a standard privilege held by most Jenkins users in typical multi-user deployments. No public exploit code has been identified at time of analysis, and CISA SSVC classifies exploitation as none currently, though technical impact is rated total given unconstrained file read on the controller.
Authentication bypass in the Jenkins SAML Plugin (all versions through 4.618.v441a_27fa_46d2) allows any authenticated low-privilege user to overwrite the SAML identity provider metadata file via unrestricted Stapler data binding, replacing it with attacker-controlled content. Once the IdP metadata is replaced, the attacker operates their own SAML authority and can issue assertions claiming any Jenkins user identity - including administrator - granting full platform compromise. No active exploitation is confirmed (not in CISA KEV), and no public POC has been identified at time of analysis.
Path traversal via Stapler data binding in Jenkins ThinBackup Plugin 2.1.4 and earlier allows authenticated low-privileged attackers to overwrite the plugin's backup configuration, redirecting backup output to an attacker-specified directory and injecting arbitrary Jenkins controller filesystem files into backup archives. The primary risk is exfiltration of high-value Jenkins controller secrets - credentials.xml, SSH keys, API tokens, master.key - via the backup mechanism. SSVC rates exploitation as none with no public exploit identified; however, the C:H impact makes this a significant post-initial-access escalation path on CI/CD infrastructure.
Stored cross-site scripting in Jenkins SonarQube Scanner Plugin ≤2.18.3 allows attackers holding Item/Configure permission to inject javascript: scheme URLs into dashboard links the plugin constructs from SonarQube scanner results. The plugin performs no URL-scheme validation, so a malicious javascript: payload persists in the Jenkins UI and executes in any victim's browser that views or interacts with the affected dashboard link. No public exploit or active exploitation has been identified at time of analysis; the Jenkins security team confirmed and published this issue on 2026-09-02.
Session fixation in Jenkins 2.579 and earlier (LTS 2.568.2 and earlier) allows an attacker who can serve content on the same site as Jenkins to inject a known session cookie into a victim's browser; when the victim subsequently authenticates via the persistent 'remember me' cookie without session rotation, the attacker inherits the fully authenticated session. The attack chain requires low-privilege same-site content delivery access and active victim participation in a remember-me login flow, meaningfully constraining real-world exploitability. Vendor patches (Jenkins 2.580 and LTS 2.568.3) are available per the Jenkins Security Advisory published 2026-09-02; no public exploit code or CISA KEV listing exists at time of analysis.
Unsafe Java deserialization in Jenkins 2.579 and earlier (LTS 2.568.2 and earlier) allows authenticated users with configuration-submission permissions to control the values of transient fields during deserialization, with impact ranging up to full server compromise depending on how those fields are used internally. Transient fields in Java are normally excluded from serialization to protect derived or sensitive state; this flaw breaks that guarantee when processing externally supplied configuration data. No public exploit code or active exploitation has been confirmed at time of analysis, but given Jenkins' role as a CI/CD orchestrator with broad network access and secrets, the blast radius of exploitation is significant.
CSRF token leakage in Jenkins allows an attacker who controls any same-origin page on the Jenkins controller to silently steal a valid CSRF crumb from an authenticated user's session and forge privileged requests on their behalf. The vulnerability spans Jenkins 2.447-2.579 (weekly) and LTS 2.452.1-2.568.2 via the bundled Stapler web framework, which embeds the session crumb as a plaintext string literal inside dynamically generated JavaScript responses. No public exploit or CISA KEV listing is present at time of analysis, but successful exploitation yields full account-level action forgery against any authenticated victim who visits the attacker-controlled page.
Stored XSS in Jenkins' system log viewer exposes administrators and privileged users to session hijacking and UI redress attacks, exploitable by any attacker who controls a Jenkins agent process. The vulnerability affects Jenkins 2.579 and earlier (including LTS 2.568.2 and earlier), where log record metadata - source, level, and timestamp - is rendered in the browser without HTML escaping, allowing persistent JavaScript injection via agent-controlled log channels. Patch versions 2.580 (weekly) and LTS 2.568.3 are available per the Jenkins security advisory SECURITY-3967; no public exploit code or CISA KEV listing has been identified at time of analysis.
Unsafe type instantiation during form data binding in Jenkins Stapler allows low-privileged authenticated users to trigger instantiation of arbitrary object types unrelated to the intended field type, achieving full compromise (C:H/I:H/A:H) of the Jenkins controller. Affected are Jenkins 2.579 and earlier and LTS 2.568.2 and earlier, via Stapler 2107.v8dfcb_e8ed317 and earlier (excluding the backport 2088.2093.vd7c3e58008a_6). The root cause is CWE-502-class unsafe deserialization/type-binding: Stapler fails to constrain which Java types may be instantiated when processing attacker-controlled HTTP form submissions. No public exploit code or CISA KEV listing is identified at time of analysis, but Jenkins is pervasively deployed in CI/CD pipelines and the low privilege bar (Overall/Read) makes this a high-priority patch target.
Remote code execution in Jenkins 2.579 and earlier (LTS 2.568.2 and earlier) allows any low-privileged authenticated user to compromise the Jenkins controller by submitting a crafted `config.xml` document. The document embeds objects that Jenkins treats as independent top-level configuration types - such as job definitions or global settings - as nested field values; once bound into Jenkins' runtime object graph, Stapler (Jenkins' HTTP routing framework) begins dispatching live HTTP requests through those embedded objects, providing an attacker-controlled code execution path. Vendor-released patches (Jenkins 2.580, LTS 2.568.3) are available as of 2026-09-02; no KEV listing or public POC is confirmed at time of analysis.
Server-Side Request Forgery in PraisonAI's Jobs API (pip/praisonai < 4.6.58) results from two compounding flaws: a fail-open DNS error handler in `JobSubmitRequest.validate_webhook_url()` that silently accepts any webhook URL when `socket.gaierror` is raised, and a TOCTOU race where `JobExecutor._send_webhook()` performs a completely independent DNS resolution via `httpx.AsyncClient` minutes to hours after validation. Authenticated attackers with a valid API bearer token can submit a job whose `webhook_url` hostname returns NXDOMAIN at validation time, then update DNS to a private IP before job completion, causing the executor to POST job result data to internal infrastructure. A detailed proof-of-concept is publicly available in GHSA-rg5q-pp8p-f7jm; no public exploit identified at time of analysis beyond the PoC, and this CVE is not listed in CISA KEV.
Remote code execution via CSRF in Jenkins Multijob Plugin 669.v9d96a_d9c71b_0 and earlier allows a network attacker to execute arbitrary code within the Jenkins controller JVM by inducing a low-privileged authenticated user to trigger a forged request. The Jenkins security advisory published 2026-08-05 formally discloses this as SECURITY-3823(2), with EUVD-2026-53526 corroborating the affected version range. No public exploit code or CISA KEV listing has been identified at time of analysis, though the network reachability and low attack complexity make this a meaningful risk wherever Jenkins is accessible and users browse untrusted sites within the same browser session.
Remote code execution on the Jenkins controller is achievable by attackers holding Agent/Connect permission via a JEP-200 deserialization filter bypass in the Remoting library (agent.jar/remoting.jar). Jenkins 2.575 and earlier, and LTS 2.568.1 and earlier, include a Remoting version (3384.v60d89463d9e0 and earlier, except the backport 3355.3357.v931d3c992987) that fails to apply the JEP-200 class filter to a fallback deserialization code path, allowing crafted serialized Java objects to reach classes on the Jenkins core classpath that are not blocked by the pre-JEP-200 denylist. No public exploit or CISA KEV listing has been identified at time of analysis, but the primitive - controller-side code execution triggered from an agent - represents a critical trust-boundary violation in Jenkins' controller-agent architecture.
Remote code execution, arbitrary file write, and privilege escalation vulnerabilities in Jenkins core (through 2.575 / LTS 2.568.1) and multiple plugins expose CI/CD infrastructure to full controller compromise. The most critical issue (CVE-2026-70426) allows agent processes and users with Agent/Connect permission to bypass the JEP-200 deserialization class filter via an unguarded fallback path in the Remoting library, enabling code execution on the Jenkins controller. Two independent arbitrary file write vectors (CVE-2026-70427 via malicious tar archives, CVE-2026-70428 via path traversal in file parameter names) can achieve equivalent controller-level code execution by writing Groovy scripts to JENKINS_HOME/init.groovy.d/ or deploying rogue plugins. No CISA KEV listing or public exploit has been identified at time of analysis, though the Jenkins security team coordinated a pre-announcement, suggesting no known active exploitation at disclosure.
Unsandboxed Groovy script execution in Jenkins Multijob Plugin 669.v9d96a_d9c71b_0 and earlier allows any attacker holding Item/Create or Item/Configure permission to run arbitrary code directly on the Jenkins controller JVM. The plugin exposes Groovy scripting capabilities that intentionally bypass the Script Security Plugin - the standard Jenkins mechanism for confining script execution to a restricted sandbox - meaning scripts execute with the full privileges of the Jenkins service account. The fix is available in Multijob Plugin 677.v7ffc23d6a_4c2; no public exploit has been identified at time of analysis and this CVE is not listed in the CISA KEV catalog.
Server-side request forgery and OIDC token forgery in Eclipse CSI PIA lets an unauthenticated attacker abuse a flawed Jenkins issuer allowlist (a bare `startswith('https://ci.eclipse.org')` check in `is_issuer_known`, pia/models.py:139) to redirect OIDC discovery and JWKS fetches to an attacker-controlled host. By posting a crafted issuer such as `https://ci.eclipse.org@evil.host` or `https://ci.eclipse.org.evil.host` to `POST /v1/upload/sbom`, an attacker forces PIA to make outbound requests to arbitrary hosts and to accept a JWT signed with the attacker's own key, effectively bypassing token verification. No public exploit identified at time of analysis, but the flaw is unauthenticated and network-reachable, and the CVSS 3.1 base score is 8.2.
XML external entity (XXE) injection in the Jenkins Assembla Plugin version 1.4 and earlier lets an attacker who can control the HTTP responses of the configured Assembla server read sensitive files and secrets from the Jenkins controller and pivot into internal services via server-side request forgery. Mapped to CWE-918 (SSRF) with a CVSS 3.1 base score of 7.1 (high), there is no public exploit identified at time of analysis and CISA SSVC rates exploitation as 'none' with only partial technical impact. Exploitation requires the attacker to influence what the Assembla endpoint returns, so it is a targeted rather than mass-exploitable condition.
Arbitrary code execution on the Jenkins controller affects the Jenkins OWASP ZAP Plugin version 1.0.7 and earlier, which incorrectly runs build operations on the controller node instead of the designated build agent. An attacker holding Item/Configure permission can leverage this misplaced execution to run arbitrary code in the security context of the controller, escaping agent isolation. No public exploit identified at time of analysis, and CISA SSVC records no known exploitation; EPSS is low at 0.39% (31st percentile).
Path traversal in the Jenkins External Workspace Manager Plugin (versions 1.3.2 and earlier) lets an attacker with Item/Configure permission supply traversal sequences in the custom workspace path of the exwsAllocate Pipeline step to read arbitrary files from the Jenkins controller filesystem, which the vendor notes can escalate to remote code execution. The flaw requires an authenticated low-privileged user (CVSS:3.1 PR:L, base 8.8) and is reported directly by the Jenkins security team. No public exploit identified at time of analysis, and CISA SSVC marks exploitation as none.
Sandbox escape in Jenkins Script Security Plugin 1402.v94c9ce464861 and earlier allows users permitted to run sandboxed Groovy scripts to execute arbitrary code outside the sandbox. The plugin fails to reject Groovy AST transformation annotations that carry an 'extensions' member, so an attacker can point that member at a suitable class already on the evaluating component's classpath and have it run outside sandbox restrictions. No public exploit identified at time of analysis, and SSVC exploitation status is 'none'; EPSS is low at 0.39%.
Sandbox bypass in the Jenkins Script Security Plugin (1402.v94c9ce464861 and earlier) lets users who can supply sandboxed Groovy scripts invoke arbitrary constructors, escaping the sandbox to run unrestricted code on the Jenkins controller. The flaw stems from the plugin failing to intercept implicit type casts on elements of typed for-each loops, a subtle gap in its interception logic. Reported by the Jenkins project (SECURITY-3792) with no public exploit identified at time of analysis; EPSS is low at 0.37% and CISA SSVC records no observed exploitation.
Authenticated remote code execution in Jenkins 2.567 and earlier (LTS 2.555.2 and earlier) allows attackers with permission to submit config.xml to trigger deserialization of arbitrary core or plugin types that subsequently handle HTTP requests, enabling user impersonation, Script Console abuse, and arbitrary file reads from the controller. The flaw is tracked as a CWE-502 unsafe deserialization issue with a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit identified at time of analysis, but the vendor (Jenkins project) has issued a coordinated advisory and patched releases.
Arbitrary file write in the Jenkins Credentials Binding Plugin (version 720.v3f6decef43ea_ and earlier) lets users who can supply file or zip-file credentials to a job write files to attacker-chosen paths on the node filesystem, escalating to remote code execution when Jenkins is configured to let a low-privileged user configure such credentials for a job running on the built-in node. The flaw stems from missing file-name sanitization on the file and zip credential types. Rated CVSS 7.5 with high attack complexity (AC:H); no public exploit identified at time of analysis and the issue is not in CISA KEV.
Arbitrary file read on the Jenkins controller is possible in the Jenkins 'Pipeline: Groovy Libraries Plugin' (version 797.v90ea_a_9b_e45a_0 and earlier), where the plugin fails to prohibit symbolic links inside shared libraries. An attacker who can control the contents of a shared library consumed by a Pipeline job can plant symlinks that resolve to sensitive files (credentials, secrets, configuration) on the controller filesystem and exfiltrate them through the build. There is no public exploit identified at time of analysis, and SSVC marks exploitation status as none, so this is a patch-and-move-on issue rather than an active-exploitation emergency.
Arbitrary file disclosure in the Jenkins Email Extension Plugin (email-ext) versions 1933.v45cec755423f and earlier lets users who can control email content abuse the data-inline image attribute to supply file: URLs, causing the Jenkins controller to read local files and embed their contents as base64 inside outgoing emails. An authenticated attacker with rights to edit job email configuration or templates (CVSS PR:L) can exfiltrate controller secrets, credentials, and configuration. There is no public exploit identified at time of analysis and CISA's SSVC rates exploitation as none, but the CVSS 8.8 score and 'total' technical impact make controller secret theft a serious concern in shared Jenkins environments.
Cookie leakage in curl (libcurl) versions 7.71.0 through 8.19.0 allows remote servers to receive cookies intended for a different host when a stale custom cookie host value persists across requests. The flaw, tracked as CWE-319 (cleartext transmission of sensitive information), carries a CVSS 7.5 and SSVC 'partial' technical impact, with no public exploit identified at time of analysis and an EPSS of 0.01%.
Stored cross-site scripting in Jenkins HTML Publisher Plugin (versions 427 and earlier) lets an attacker with Item/Configure permission inject JavaScript via an unescaped job name and URL written into the legacy wrapper file, which then executes in the browser of any user who later views the published report. There is no public exploit identified at time of analysis and EPSS is very low (0.04%, 12th percentile), but the SSVC technical impact is rated total, meaning a successful payload can fully compromise a victim session such as an administrator's.
Stored cross-site scripting in the Jenkins GitHub Plugin (versions ≤ 1.46.0) lets a low-privileged authenticated user with Overall/Read permission inject JavaScript by controlling the current job URL, which is unsafely embedded into the client-side validation logic for the 'GitHub hook trigger for GITScm polling' feature. When another user — potentially a Jenkins administrator — views the affected page, the attacker's script executes inside their authenticated Jenkins session. No public exploit is identified at time of analysis and EPSS is very low (0.04%), but the CVSS 9.0 rating and scope-changed impact make it a meaningful CI/CD privilege-escalation surface.
Arbitrary file write in the Jenkins Credentials Binding Plugin (version 719.v80e905ef14eb_ and earlier) allows an authenticated user who can supply file or zip file credentials to a job to escape the intended credentials directory via unsanitized file names (path traversal), planting files anywhere on the node filesystem. When Jenkins is configured to let a low-privileged user configure such credentials for a job running on the built-in node, this file write escalates to remote code execution. There is no public exploit identified at time of analysis, and EPSS is low (0.34%, 57th percentile), consistent with the high attack complexity and non-default preconditions.
Path traversal in Allure report generator for Jenkins allows unauthenticated attackers to read arbitrary files from the host system by crafting malicious test result files with specially crafted attachment paths. The vulnerability stems from insufficient path validation when processing attachments during report generation, enabling sensitive files to be included in generated reports. A patch is not currently available.
Jenkins versions 2.442 through 2.554 and LTS 2.426.3 through 2.541.2 contain an origin validation bypass vulnerability in the CLI WebSocket endpoint that allows attackers to conduct DNS rebinding attacks. The vulnerability stems from improper use of Host and X-Forwarded-Host headers to compute expected request origins, enabling attackers to bypass authentication controls and potentially execute arbitrary commands through the CLI WebSocket interface. While no CVSS score, EPSS data, or active exploitation in the wild (KEV) status has been publicly disclosed, the vulnerability affects a critical Jenkins component and was responsibly disclosed by the Jenkins security team.
Jenkins versions 2.554 and earlier (LTS 2.541.2 and earlier) contain a path traversal vulnerability in their handling of tar and tar.gz archive extraction that fails to safely process symbolic links, allowing attackers to write files to arbitrary filesystem locations. Attackers with Item/Configure permission or control over Jenkins agent processes can exploit this to deploy malicious scripts and plugins on the Jenkins controller, achieving code execution with the privileges of the Jenkins process. The vulnerability is particularly concerning because it affects the core Jenkins application and enables privilege escalation through plugin installation mechanisms.
Jenkins versions 2.483-2.550 and LTS 2.492.1-2.541.1 contain a stored XSS vulnerability in the agent offline cause description field that fails to properly sanitize user input. Attackers with Agent/Configure or Agent/Disconnect permissions can inject malicious scripts that execute in the browsers of other users viewing the affected agent configuration. No patch is currently available for this vulnerability.
Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character followed by a file path in an argument with the file's contents,. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resources by rapidly opening and immediately canceling (RST_STREAM) large numbers of streams over a single connection, a technique dubbed the 'Rapid Reset' attack. The flaw is confirmed actively exploited (CISA KEV) following large-scale weaponization observed August through October 2023, with publicly available exploit code and an EPSS score of 94.45% placing it in the 100th percentile for likelihood of exploitation. Virtually every major HTTP/2 stack - including nghttp2, Netty, Envoy, and Eclipse Jetty - is affected.
A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.java that allows attackers able. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.53 and earlier in src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovySandbox.java,. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.50 and earlier in src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SecureGroovyScript.java that allows. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A sandbox bypass vulnerability exists in Pipeline: Declarative Plugin 1.3.3 and earlier in. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.61 and earlier in src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition.java,. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A sandbox bypass vulnerability exists in Script Security Plugin 1.49 and earlier in src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovySandbox.java that allows attackers with the. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A code execution vulnerability exists in the Stapler web framework used by Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in stapler/core/src/main/java/org/kohsuke/stapler/MetaClass.java that. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
The remoting module in Jenkins before 2.32 and LTS before 2.19.3 allows remote attackers to execute arbitrary code via a crafted serialized Java object, which triggers an LDAP query to a third-party. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and EPSS exploitation probability 89.2%.
Multiple unspecified API endpoints in Jenkins before 1.650 and LTS before 1.642.2 allow remote authenticated users to execute arbitrary code via serialized data in an XML file, related to XStream and. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 90.9%.
The Jenkins CLI subsystem in Jenkins before 1.638 and LTS before 1.625.2 allows remote attackers to execute arbitrary code via a crafted serialized Java object, related to a problematic. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and EPSS exploitation probability 90.4%.
The Fingerprints pages in Jenkins before 1.638 and LTS before 1.625.2 might allow remote attackers to obtain sensitive job and build name information via a direct request. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and EPSS exploitation probability 27.4%.
Open redirect in the Jenkins Keycloak Authentication Plugin 2.4.1 and earlier lets an unauthenticated attacker craft a login URL whose post-authentication redirect target is not validated, sending a victim who completes Keycloak login to an arbitrary external site (CWE-601, vendor CVSS 4.3). Only Jenkins instances where this plugin is installed and configured as the active authentication realm are affected, and exploitation requires the victim to click the supplied link and finish authentication (UI:R), so impact is confined to phishing and credential-harvesting rather than direct access to Jenkins. No public exploit code identified at time of analysis and no CISA KEV listing; the primary limiting factors are the mandatory user interaction and the low-integrity impact assessed in the vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N.
Stored cross-site scripting (XSS) in the Jenkins Gitee Plugin (versions up to and including 1301.v8957053c7902) allows an authenticated attacker who can trigger builds via the plugin's push webhook and control the sender name field to inject malicious JavaScript into build causes, which executes when a Jenkins user views the affected build's causes page. The vulnerability requires the plugin's webhook endpoint to be reachable and a user to subsequently view the build page (UI:R). No public exploit code has been identified at time of analysis, and the vendor's CVSS score of 6.8 uses a boilerplate vector; independent assessment rates it as CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N.
Server-side request forgery in the Jenkins Bitbucket Push and Pull Request Plugin (4.0.1 and earlier) lets remote attackers submit a crafted webhook payload whose attacker-controlled URL Jenkins then contacts using the Bitbucket credentials stored in the plugin's configuration, exposing those credentials. Per the vendor CVSS vector (AV:N/AC:L/PR:N/UI:N) the attack is remote, low-complexity, and requires no authentication or user interaction; our independent assessment rates the confidentiality impact as high because successful exploitation yields the stored Bitbucket credential material itself. Exploitation is only possible on Jenkins instances where the plugin is installed, reachable on its webhook trigger endpoint, and actually configured with Bitbucket credentials; no public exploit code has been identified at time of analysis and there is no KEV listing for this CVE.
OAuth flow hijacking in the Jenkins Bitbucket Server Integration Plugin 6.0.1 and earlier allows an attacker to substitute the callback URL used in the plugin's OAuth authorization step and capture the Bitbucket access token issued to a victim. Exploitation is not against a static endpoint: the plugin must be installed with its OAuth authorization flow in active use, the attacker must have an OAuth handshake in progress, and a victim who is already authenticated must complete the authorization step (UI:R) within a timing window the attacker must hit (AC:H). Rated only CVSS 4.2 with no confidentiality or integrity impact beyond the scope of the hijacked victim's token, this is a genuine authentication-flow flaw but a low-priority one; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Credential isolation bypass in Jenkins GitLab Plugin 1.2149.vcfc32c82b_f7f and earlier allows an authenticated user who holds Item/Configure permission on a folder to reach 'alternative GitLab API token credentials' that are scoped to a different folder and that they are not entitled to use, because the plugin caches the GitLab API client under a cache key derived solely from the credentials ID and never incorporates the folder in which the credentials were resolved. Rated CVSS 3.1 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) under CWE-522 (insufficiently protected credentials), the issue is a moderate authorization/credential-isolation flaw rather than an unauthenticated remote compromise, and it only exists on multi-tenant Jenkins controllers that actually rely on folder-scoped credentials - single-tenant installations and controllers where all credentials are global/system-scoped see no practical impact. There is no public exploit identified at time of analysis, CISA SSVC records Exploitation: none and Automatable: no, and the CVE is not KEV-listed, so it warrants scheduled patching rather than emergency response.
Information disclosure in Jenkins Gradle Plugin 2.19.1252.v15196b_5a_6e10 and earlier lets an authenticated Jenkins user who can influence the build log of a Gradle job trick the plugin into fetching build scan data from an attacker-controlled URL in preference to the Develocity server URL set in the plugin's global configuration. Because the plugin attaches the globally configured Develocity access key to that outbound request, the attacker can capture the credential; instances with no Develocity access key configured have nothing to leak, so exposure is conditional rather than universal. No public exploit code has been identified at time of analysis, and this is a genuine but moderate-severity issue: exploitation requires authenticated job-run or job-configure privileges plus a configured access key, and the resulting impact is limited to confidentiality (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
Path traversal in the Jenkins Pipeline: Groovy Libraries Plugin (805.va_fc79344957d and earlier) lets an authenticated user who can configure Pipelines point the `library` step at a path outside the SCM checkout and follow symbolic links, giving read access to files in a resources directory and the ability to delete files in a test directory on the Jenkins controller file system. Exploitation requires the Pipeline-configuration privilege, a symlink placed inside the checkout, and successful traversal during library retrieval, which is reflected in the high attack complexity of the assessed CVSS:3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, base score 4.2). No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), so the practical risk is low-to-moderate and confined to file read and limited file deletion rather than arbitrary write or code execution.
Credential disclosure in Jenkins Pipeline: Multibranch Plugin 841.vec5b_9e1806ec and earlier allows users who already hold Item/Configure permission to capture credentials they are not entitled to by authoring or modifying a Pipeline that invokes the resolveScm step, which fails to establish the correct context for credentials lookup. The issue is an access-control scoping flaw (CWE-863) rated CVSS 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N), reflecting the authenticated Item/Configure prerequisite, the high complexity of targeting specific credential IDs, and impact limited to confidentiality with no integrity or availability effect. It requires a Jenkins instance that actually uses Pipeline/multibranch jobs with resolveScm; at time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified, though the vendor advisory of 2026-09-16 should be reviewed for the fixed release.
Stored cross-site scripting in Jenkins update-center2 3.18.3 and earlier allows an attacker who can submit a plugin for hosting to inject malicious script into plugin download index pages by embedding payloads in plugin names, descriptions, or version metadata. Any user who browses the affected plugin index page triggers the XSS payload in their browser session. No exploitation has been confirmed (SSVC: none, no KEV), and no public exploit code has been identified at time of analysis.
Plaintext token storage in Jenkins Parameterized Remote Trigger Plugin 3.2.2 and earlier exposes authentication tokens to any Jenkins user holding Item/Extended Read permission or to anyone with direct access to the Jenkins controller filesystem. Tokens written to job config.xml files are readable without decryption, potentially allowing lower-privileged users to impersonate legitimate remote-trigger callers and invoke builds on downstream Jenkins instances. No public exploit has been identified; SSVC assessment confirms no active exploitation and a non-automatable attack path.
Missing authorization checks in Jenkins XebiaLabs XL Deploy Plugin 26.1.0 and earlier permit any authenticated Jenkins user holding Overall/Read permission to enumerate the IDs of credentials stored in the Jenkins Credentials store. Although credential values (passwords, tokens, certificates) are not directly exposed, the disclosed identifiers constitute reconnaissance data that could guide follow-on attacks against CI/CD pipeline secrets. No public exploit is identified at time of analysis and SSVC rates exploitation as none with partial technical impact.
Unauthorized configuration overwrite in Jenkins Job Configuration History Plugin (≤1367.vc8fa_b_15101dc) permits any authenticated low-privilege user to redirect the plugin's audit history storage to an attacker-specified filesystem directory and alter history recording settings via unsanitized Stapler data binding. By controlling the storage path, an attacker can corrupt or suppress configuration change audit trails, or potentially access sensitive directory contents at the redirected path. No public exploit code exists and EPSS stands at 0.15% (4th percentile), indicating low real-world exploitation pressure at this time.
Configuration integrity compromise in Jenkins GitLab Plugin 1.9.16 and earlier enables authenticated low-privileged users to overwrite the global GitLab connection URL via Stapler data binding, redirecting GitLab API calls to attacker-controlled infrastructure. This causes Jenkins to transmit administrator-configured GitLab API tokens to the attacker's endpoint whenever a pipeline, webhook, or scheduled job triggers a GitLab API interaction. No KEV listing or public exploit has been identified at time of analysis, but the low privilege bar means any Jenkins account holder can abuse this on unpatched installations.
Cross-site request forgery in Jenkins Pipeline: Groovy Libraries Plugin 798.v5cc688825312 and earlier allows unauthenticated remote attackers to delete shared library caches by tricking an authenticated Jenkins user into visiting a malicious page. The impact affects pipeline integrity and build availability, as deleted caches force library re-fetching and can disrupt CI/CD workflows. No public exploit or KEV status has been identified at time of analysis; the vulnerability was disclosed by Jenkins in its September 2, 2026 security advisory (SECURITY-3815).
Server-side request forgery in Jenkins LDAP Plugin 807.809.vd3a_4e5e4ec98 and earlier allows low-privileged authenticated attackers to cause the Jenkins server to initiate connections to arbitrary, attacker-specified URLs via unsanitized Stapler data binding on the LDAP configuration endpoint. This enables internal network probing or interaction with attacker-controlled infrastructure from the Jenkins server's network perspective. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Unauthorized build cancellation in Jenkins Pipeline: Build Step Plugin 599.v4b_67ea_11b_152 and earlier allows any authenticated low-privilege user to cancel downstream pipeline builds they should not be able to touch. When a pipeline uses the `waitForBuild` step with the `propagateAbort` parameter enabled, aborting the upstream build propagates a cancel signal to downstream jobs without verifying whether the caller holds the required Item/Cancel permission on those downstream jobs. No public exploit has been identified at time of analysis, and EPSS data was not provided in the input.
Missing Item/Cancel permission enforcement in Jenkins Pipeline: Build Step Plugin ≤599.v4b_67ea_11b_152 allows authenticated low-privilege users to cancel downstream builds they are not authorized to abort. When an upstream pipeline job using the `build` step is canceled, the plugin propagates the cancellation to all triggered downstream jobs without verifying that the build's authentication context holds Item/Cancel permission on those downstream jobs. Jenkins reported this in their 2026-09-02 security advisory (SECURITY-3870); no public exploit code has been identified at time of analysis.
Jenkins Script Security Plugin 1412.v7737b_3405f86 and earlier allows any low-privileged authenticated Jenkins user to disable the 'Force the use of the sandbox globally in the system' security control via a missing permission check exposed through Stapler data binding. The CVSS score of 4.3 reflects only the direct act of altering a setting, but the chained real-world risk is substantially higher: disabling global sandbox enforcement removes the primary defense against unrestricted Groovy execution, enabling subsequent RCE by any user with script authorship rights. No public exploit has been identified at time of analysis, and exploitation has not been confirmed by CISA KEV.
Improper use of the @DataBoundConstructor annotation in Jenkins Script Security Plugin versions ≤1412.v7737b_3405f86 enables low-privileged authenticated users to read the plugin's script approval configuration by submitting certain Jenkins forms. The flaw allows enumeration of which Groovy scripts, methods, and signatures have been approved for execution - information that could assist an attacker in mapping permitted scripted operations within the Jenkins environment. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code has been identified at the time of analysis.
Missing authorization in Jenkins' CLI build command allows authenticated low-privileged users to cancel builds they did not initiate. When invoking the `build` CLI command with the `-s` flag (wait-for-completion mode), Jenkins 2.579 and earlier and LTS 2.568.2 and earlier skip the required `Item/Cancel` permission check, enabling any user holding only `Item/Build` permission to abort in-flight builds owned by other users. No public exploit code has been identified at time of analysis, and this issue is not listed in the CISA KEV catalog.
Missing authorization (CWE-862) in Jenkins 2.579 and earlier (LTS 2.568.2 and earlier) permits any authenticated user holding Item/Read on at least one job to read build parameter names and values from jobs they are not authorized to access. The CVSS vector (PR:L, AV:N, AC:L) confirms low-complexity, network-accessible exploitation requiring only a minimal authenticated foothold. Patched releases (2.580 weekly, LTS 2.568.3) are available per the official vendor advisory; no public exploit or CISA KEV listing has been identified at time of analysis.
Jenkins REST API in versions 2.579 and earlier (LTS 2.568.2 and earlier) fails to escape map keys during JSON and Python serialization, enabling authenticated users who can control map property names to inject arbitrary fields into API responses consumed by downstream tooling or users. The flaw (CWE-116, improper output encoding) is rated CVSS 4.3 Medium with integrity-only impact and requires low-privilege authenticated access. No public exploit code or CISA KEV listing has been identified; vendor patches 2.580 and LTS 2.568.3 were released on 2026-09-02.
Static field manipulation in Jenkins' Stapler web framework (SECURITY-3926) allows authenticated users who can submit configuration forms to set public static fields on bound configuration objects, causing changes that propagate globally across the entire Jenkins instance and affect all users and build pipelines. Affected releases are Jenkins 2.579 and earlier (weekly) and LTS 2.568.2 and earlier, with fixed versions 2.580 and LTS 2.568.3 released in the 2026-09-02 security advisory. No public exploit code has been identified and the vulnerability does not appear in CISA KEV, but the global-state impact of successful exploitation exceeds what the per-session CVSS 5.4 score alone suggests.
Improper permission enforcement in Jenkins's Appearance configuration page allows authenticated users holding the Overall/Manage permission to modify Appearance configuration options beyond their authorized scope. Affected are Jenkins 2.579 and earlier (weekly) and LTS 2.568.2 and earlier. The vendor has released fixes in Jenkins 2.580 and LTS 2.568.3; no public exploit or active exploitation has been identified, and EPSS places this at the 6th percentile of exploitation likelihood.
Agent configuration takeover in Jenkins 2.579 and earlier allows an attacker holding Agent/Configure permission on any single agent to overwrite any other agent's configuration by embedding the target agent's name in a crafted XML document submitted to the REST API or CLI update endpoints. Successful exploitation grants the attacker full control of the victim agent's configuration and exposes its inbound agent secret and environment variables - primitives that enable agent impersonation and lateral movement within the CI/CD infrastructure. No public exploit code or CISA KEV listing has been identified at time of analysis; patches are available as Jenkins 2.580 and LTS 2.568.3.
XML deserialization in Jenkins 2.579 and earlier (LTS 2.568.2 and earlier) allows any authenticated user holding the minimal Overall/Read permission to inject crafted XML that causes the server to instantiate user objects as nested field values within other deserialized structures, producing unauthorized modifications to the Jenkins user database. The root cause is CWE-502 - insufficient type filtering during XML deserialization - which permits user-typed objects to be materialized outside normal user-creation workflows. No active exploitation has been confirmed by CISA KEV, and no public exploit code has been identified; patched releases (2.580 weekly, 2.568.3 LTS) are available per the Jenkins security advisory.
CVE-2026-70443 is part of the Jenkins August 5, 2026 batch security advisory covering Jenkins core and multiple plugins. The provided source data does not include the specific vulnerability description for CVE-2026-70443 - the advisory text is truncated before reaching this CVE identifier (described CVEs end around CVE-2026-70435). The full advisory at https://www.jenkins.io/security/advisory/2026-08-05/ contains authoritative details. No active exploitation is confirmed (not listed in CISA KEV), and no EPSS or CVSS data was provided in the source intelligence.