dbcve.org
JenkinsApplication

CVE-2026-53441

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 2.555.3 / 2.568 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Jenkins fails to sanitize the user-provided description field for a generic offline cause before rendering it in the web UI. Attackers with Agent/Configure permissions can inject malicious JavaScript via the POST config.xml API, which executes when other users view the offline cause description.

MitigationUpgrade Jenkins to version 2.568 or later (LTS 2.555.3 or later) which includes proper HTML escaping for the offline cause description field.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JenkinsApplication
Affected:>= 2.483, < 2.568>= 2.492.1, < 2.555.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Jenkins version
    Navigate to Manage Jenkins > About Jenkins (or access /whoAmI/api/json) to view the running version number
    Affected if The version falls within 2.483 to 2.567.x, 2.492.1 to 2.555.2, or any version below 2.568 that is not LTS 2.555.3 or later
  2. Identify configured agents with offline causes
    Navigate to Manage Jenkins > Nodes. Review each agent's status for any that show as offline with a custom cause description
    Affected if Any agents display an offline status with a non-empty description field that you did not personally configure
  3. Inspect agent config.xml for suspicious description content
    Access each agent's config.xml via /computer/(agent-name)/config.xml and examine the <offlineCause> or <description> fields for HTML/script tags
    Affected if The XML contains unescaped HTML tags such as <script>, <img>, <svg>, or javascript: URLs in the offline cause description
  4. Verify permission configuration for Agent/Configure
    Navigate to Manage Jenkins > Manage Users > [select user] > Permissions, or check /whoAmI/api/json for current user permissions
    Affected if Users other than administrators have Agent/Configure or Overall/Administer permissions enabled
  5. Review recent config.xml API changes
    Check Jenkins logs for POST requests to /computer/(agent-name)/config.xml, or examine version control/history for recent changes to node configurations
    Affected if Recent config.xml modifications include description fields with encoded or raw HTML content

A user is affected if their Jenkins version is in the vulnerable range AND agents exist with offline cause descriptions that contain unescaped HTML or script content viewable by multiple users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.555.3 / 2.568 or later
Fixed in 2.555.32.568
Interim mitigation

Upgrade Jenkins to version 2.568 or later (LTS 2.555.3 or later) which includes proper HTML escaping for the offline cause description field.

Recommended fix High confidence

Jenkins 2.568 (weekly) or Jenkins 2.555.3 (LTS)

  1. Identify which Jenkins release line is in use: weekly releases or LTS (Long-Term Support)
  2. For Jenkins weekly releases: upgrade to Jenkins 2.568 or later
  3. For Jenkins LTS releases: upgrade to Jenkins 2.555.3 or later
  4. After upgrade, verify the fix by confirming the generic offline cause description is properly escaped in the UI
  5. If using automated config management, ensure the config.xml API payload is validated before upgrade to avoid triggering the vulnerable code path
Caveat No known breaking changes for this security update; standard minor version upgrade applies

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53441 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53441 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data