LiveActive security incident?Get immediate response
CVE Record

CVE-2026-53435: In Jenkins 2.567 and earlier, LTS 2.555.2 and earlier, it is possible for attackers to have Jenkins deseria...

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.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Jenkins flaw can let a logged-in attacker abuse a submitted config.xml file so Jenkins acts as another user. If the attacker reaches an administrator-equivalent action, impact can include arbitrary code execution or file disclosure on the Jenkins controller.

Executive priority

Treat this as a high-priority Jenkins remediation. It is not confirmed as exploited in the supplied sources, but successful abuse could compromise build infrastructure, secrets, deployments, and source-code access.

Technical view

CVE-2026-53435 is a Jenkins deserialization issue involving attacker-controlled config.xml submissions. Affected versions are Jenkins 2.567 and earlier and LTS 2.555.2 and earlier. The issue can allow handling HTTP requests as another user, potentially reaching Script Console execution or controller file reads.

Likely exposure

Organizations running Jenkins controllers at 2.567 or earlier, or LTS 2.555.2 or earlier, are the likely exposed population. The CVSS vector indicates network access with low complexity but requires privileges.

Exploitation context

The bundle does not cite active exploitation and KEV is false. The described attack requires an authenticated attacker able to submit attacker-controlled config.xml content. Potential impact is severe because Jenkins often holds build secrets, source access, and deployment permissions.

Researcher notes

Key evidence is from the CVE record and Jenkins advisory summary. The supplied bundle names impact and affected ranges but does not include full patch or workaround text. Avoid assuming plugin-specific exposure beyond arbitrary types defined in Jenkins core or plugins.

Mitigation direction

  • Review the Jenkins advisory for the vendor-approved fixed versions and upgrade path.
  • Inventory Jenkins controllers and identify versions 2.567 or earlier and LTS 2.555.2 or earlier.
  • Restrict Jenkins administrative and configuration privileges to trusted users only.
  • Review Jenkins controller logs for suspicious configuration submissions or unexpected user impersonation behavior.
  • Temporarily limit network access to Jenkins management interfaces where feasible.

Validation and detection

  • Confirm each Jenkins controller version against the affected version ranges in the advisory.
  • Review users and groups with permissions to create or modify Jenkins configuration.
  • Check whether Script Console access is limited to expected administrators.
  • Audit recent config.xml changes for unexpected submitters or timing.
  • Confirm remediation by rechecking Jenkins version after upgrade or vendor-directed mitigation.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-53435 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADP
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-53435Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPjenkins: Jenkins: Arbitrary code execution via deserialization of attacker-controlled configuration
other:Red Hat severity ratingcvssV3_1
  • 2026-06-10T14:01:29.010Z: Reported to Red Hat.
  • 2026-06-10T13:05:57.208Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Jenkins ProjectJenkins2.568, 2.555.3affected
Weakness

CWE details

CWE-502

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs