CVE-2026-53441
jenkins: Jenkins: Stored Cross-Site Scripting (XSS) via unescaped user-provided description
Overview
Description
Jenkins 2.483 through 2.567 (both inclusive), LTS 2.492.1 through 2.555.2 (both inclusive) does not escape the user-provided description of a generic offline cause that could be set through the POST config.xml API, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Agent/Configure permission.
Source: OX vulnerability database
Severity
5.4 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Weakness: CWE-79
Affected packages · 2
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Bitnami | jenkins | >=2.483.0, <2.555.3>=2.556.0, <2.568.0 | 2.555.32.568.0 |
| Maven | org.jenkins-ci.main:jenkins-core | >=2.483, <2.568 | 2.568 |
Open a package to see all its vulnerabilities.
Operating systems · 4 fixes
alpine 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| edge | jenkins | 2.555.3-r0 |
chainguard 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| jenkins-2-555 | 2.555.3-r0 |
minimos 1 release · 2 packages
| Release | Package | Fixed in |
|---|---|---|
| jenkins-2-555 | 2.555.3-r0 | |
| jenkins | 2.568-r0 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2026-53441
- github.com https://github.com/jenkinsci/jenkins
- github.com https://github.com/jenkinsci/jenkins/commit/20041e8090d3b228d586169141ea7f12ffe4444d
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2026-53441
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2026-53441
- www.jenkins.io https://www.jenkins.io/security/advisory/2026-06-10/#SECURITY-3731
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.