dbcve.org
JenkinsApplication

CVE-2026-53442

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

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.567 and earlier, LTS 2.555.2 and earlier does not encrypt secrets from POST config.xml submissions before storing them in job configurations unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Item/Extended Read permission, or access to the Jenkins controller file system.

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 versions 2.567 and earlier and LTS 2.555.2 and earlier fail to encrypt secrets submitted via POST config.xml requests before storing them in plaintext in job config.xml files on the controller filesystem, exposing credentials to users with Item/Extended Read permission or anyone with file system access.

MitigationUpgrade Jenkins to a patched version. In the interim, restrict Item/Extended Read permissions to minimal necessary users and limit filesystem access to the Jenkins controller.

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.555.3< 2.568

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 /api/json?tree=version to retrieve the installed version number
    Affected if version is 2.567 or earlier, or LTS 2.555.2 or earlier (for LTS, check if version is 2.555.x where x <= 2)
  2. Locate job config.xml files
    Browse to $JENKINS_HOME/jobs/<jobname>/config.xml for each job directory on the controller filesystem
    Affected if config.xml files exist in job directories
  3. Inspect config.xml for plaintext secrets
    Open config.xml files and search for plaintext password, secret, or credential fields (look for <password>, <secret>, or credential-related XML elements that contain unencrypted string values)
    Affected if any config.xml contains plaintext passwords, API tokens, or secrets in cleartext rather than encrypted form
  4. Check API access patterns
    Review Jenkins access logs or audit records for POST requests to /job/<name>/config.xml endpoints that may have submitted credentials
    Affected if config.xml API was used to update job configurations containing secrets

You are affected if running a Jenkins version 2.567/2.555.2 or earlier AND any job config.xml files contain unencrypted plaintext passwords, secrets, or credentials.

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 a patched version. In the interim, restrict Item/Extended Read permissions to minimal necessary users and limit filesystem access to the Jenkins controller.

Recommended fix High confidence

Jenkins LTS 2.555.3+ or Jenkins 2.568+

  1. Review the Jenkins LTS upgrade guide and release notes at https://www.jenkins.io/doc/upgrade-guide/
  2. Ensure you have a complete backup of the Jenkins home directory ($JENKINS_HOME) including all job configurations and secrets
  3. Schedule a maintenance window as Jenkins will restart during upgrade
  4. Download Jenkins LTS 2.555.3 or later (or weekly release 2.568 or later) from https://www.jenkins.io/download/
  5. If using the WAR file, replace the existing jenkins.war and restart the Jenkins service
  6. If using native packages, upgrade via your package manager (apt, yum, yum, etc.) and restart the Jenkins service
  7. After restart, verify the upgrade by checking the Jenkins version at: Manage Jenkins > About Jenkins
  8. To confirm the fix, submit a secret via POST config.xml and verify the job config.xml file no longer contains the secret in plaintext (accessible to users with Item/Extended Read permission)
Caveat Standard Jenkins upgrade considerations apply - review plugin compatibility and test in staging if possible

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

Fix this in Jenkins Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53442 — 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-53442 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