---
id: "CVE-2026-117612"
kind: "vulnerability"
aliases: ["CVE-2026-117612"]
title: "Jenkins: deserialization filter skipped for classes named in resolves-to"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["ci-cd", "jenkins", "runtime", "self-hosted"]
not_affected_if: ["patched-version"]
published_at: "2026-10-28T17:18:20+00:00"
first_seen_at: "2026-10-28T17:34:09+00:00"
updated_at: "2026-10-28T17:35:01+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-117612", "first_seen_at": "2026-10-28T17:34:09+00:00"}]
---

# Jenkins: deserialization filter skipped for classes named in resolves-to

Jenkins does not apply its XStream deserialization filter to classes referenced by the resolves-to attribute, so the filter that normally blocks dangerous classes is bypassed for them. The sources do not say what an attacker gets beyond the deserialization bypass, so code execution is not confirmed.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the running Jenkins version with `jenkins-cli version` or the footer of the web UI, and compare it against `2.587` (weekly) and `2.580.1` (LTS).
- unknown

## Fix

- Upgrade Jenkins weekly to a release later than `2.587`, or LTS to a release later than `2.580.1`.
- unknown

## Timeline

- 2026-10-28T17:34:09+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-117612

## From the sources

Jenkins 2.587 and earlier, LTS 2.580.1 and earlier does not apply its deserialization filter to classes referenced by the `resolves-to` attribute during XStream deserialization.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_