dbcve.org
JenkinsApplication

CVE-2026-53435

HIGH · 8.8 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 2.555.3 / 2.568 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
In Jenkins 2.567 and earlier, LTS 2.555.2 and earlier, it is possible for attackers to have Jenkins deserialize arbitrary types defined in Jenkins core or plugins from an attacker-controlled `config.xml` submission in a way that allows them to handle HTTP requests afterwards. This can be used to impersonate any user and send HTTP requests on their behalf, up to and including use of the Script Console to run arbitrary code, or to read arbitrary files from the Jenkins controller.

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

This is a Java deserialization vulnerability where Jenkins deserializes arbitrary types from attacker-controlled config.xml submissions without proper validation. Attackers can exploit gadget chains in Jenkins core or plugins to achieve remote code execution via the Script Console, read arbitrary files from the controller, or impersonate users by hijacking their sessions.

MitigationUpgrade Jenkins to a version beyond 2.567 (or LTS beyond 2.555.2) that contains the patched deserialization logic. Restrict network access to config.xml submission endpoints until the upgrade can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Identify installed Jenkins version
    Navigate to Manage Jenkins > About Jenkins, or access /api/json?tree=mode,nodeDescription,numExecutors,mode,nodeName,description,jobs/url,primaryView[{name,url}],quietingDown,slaveAgentPort,unlabeledLoad{parameters,url},useCrumbs,useSecurity,views/{name,url},builds[{number,url,result,timestamp,duration,changeSets{items{author{fullName,id},commitId,msg,timestamp}}]}
    Affected if version is below 2.555.3 (LTS) or below 2.568 (weekly)
  2. Verify config.xml submission endpoint is accessible
    Check if the endpoint /configSubmit or /job/{name}/config.xml accepts POST requests without proper deserialization safeguards. Attempt a benign test submission or review server logs for config.xml POST patterns.
    Affected if config.xml submission endpoint is exposed and accepts serialized Java objects without validation
  3. Confirm Jenkins security realm settings
    Navigate to Manage Jenkins > Configure Global Security > Security Realm. Determine if authentication is required for configuration changes and whether anonymous users have Overall/Administer permissions.
    Affected if anonymous users have elevated permissions or security is disabled, allowing unauthenticated config.xml submissions
  4. Inspect HTTP access logs for suspicious config.xml activity
    Review Jenkins access logs (typically in $JENKINS_HOME/logs) for POST requests to /configSubmit or /job/*/config.xml with unusual payload sizes or patterns indicating serialized objects.
    Affected if any POST requests to config submission endpoints are logged from untrusted sources

A system is affected if it runs Jenkins version 2.555.2 or earlier (LTS) or 2.567 or earlier (weekly) AND has config.xml submission endpoints accessible to attackers.

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 version beyond 2.567 (or LTS beyond 2.555.2) that contains the patched deserialization logic. Restrict network access to config.xml submission endpoints until the upgrade can be applied.

Recommended fix High confidence

Jenkins 2.568 (weekly) or Jenkins 2.555.3 LTS

  1. Check current Jenkins version by navigating to Manage Jenkins > About Jenkins
  2. If running a weekly release < 2.568, plan upgrade to Jenkins 2.568 or later
  3. If running LTS release < 2.555.3, plan upgrade to Jenkins 2.555.3 LTS or later
  4. Review upgrade prerequisites and backup Jenkins home directory
  5. Schedule maintenance window for upgrade
  6. Download appropriate Jenkins WAR file from https://www.jenkins.io/download/
  7. Stop Jenkins service
  8. Replace existing WAR file with new version
Caveat Review Jenkins LTS upgrade guide for compatibility with installed plugins; some plugins may require updates for LTS 2.555.3

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

Fix this in Jenkins Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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