# CVE-2026-117624: Jenkins deserialization filter bypass in XStream resolves-to attribute

Source: https://junglewise.ai/threats/cve-2026-117624-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-does-not  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-28. Updated: 2026-10-28  
License: CC BY 4.0 with a link back

CVE-2026-117624 · Severity: info · Published 2026-10-28

Jenkins is an automation server used by development teams to build and test software. This vulnerability allows attackers who have Read permission and a user account to bypass security restrictions on what types of objects can be deserialized from XML configuration files, potentially executing arbitrary code on the Jenkins server. The flaw affects how Jenkins processes configuration data from items like jobs and agents.

Technologies: [Jenkins](https://junglewise.ai/threats/technologies/jenkins). Vendors: [Jenkins](https://junglewise.ai/threats/vendors/jenkins).

## Quick answers

**Is CVE-2026-117624 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-117624 being exploited in the wild.

**How severe is CVE-2026-117624?** Informational severity, published 28 October 2026.

**Which products and versions are affected?** Jenkins 2.587 and earlier, LTS 2.580.1 and earlier.

**Is there a fix for CVE-2026-117624?** Yes: fixed in Jenkins 2.588, LTS 2.580.2. Until then: Administrators who encounter problems with the new type permission system enforcement can disable it by setting the Java system property hudson.util.XStream2.SUPPRESS_TYPE_PERMISSION to true.</anigation>
<parameter name="timeline">[{"kind":"disclosed","at":"2026-10-28"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-117624 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-117624?** Check whether you run Jenkins at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Jenkins 2.588, LTS 2.580.2

Administrators who encounter problems with the new type permission system enforcement can disable it by setting the Java system property hudson.util.XStream2.SUPPRESS_TYPE_PERMISSION to true.</anigation>
<parameter name="timeline">[{"kind":"disclosed","at":"2026-10-28"}]

## Technical details

Jenkins 2.587 and earlier uses XStream for deserialization with a custom filter (JEP-200) to restrict allowed types, but the filter is not applied to classes referenced by the resolves-to attribute. This allows instantiation of arbitrary types during deserialization of configuration XML. Attackers need Overall/Read permission plus either a user account or permissions to POST config.xml (Item/Configure, View/Configure, or Agent/Configure).

## Affected products

- Jenkins Jenkins 2.587 and earlier, LTS 2.580.1 and earlier

## References

- [https://www.jenkins.io/security/advisory/2026-10-28/](https://www.jenkins.io/security/advisory/2026-10-28/)

## Related threats

- [Jenkins path traversal in file browser workspace disclosure](https://junglewise.ai/threats/cve-2026-117626-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-improperly)
- [Jenkins missing HTTP proxy permission check](https://junglewise.ai/threats/cve-2026-117625-a-missing-permission-check-in-jenkins-2-587-and-earlier-lts-2)
- [Jenkins stored cross-site scripting in breadcrumb menu tooltips](https://junglewise.ai/threats/cve-2026-117623-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-does-not)
- [Jenkins agent XSS via Stapler HttpResponse exceptions](https://junglewise.ai/threats/cve-2026-117622-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-allows-agents)
- [Jenkins workspace browser XSS in agent URL computation](https://junglewise.ai/threats/cve-2026-117621-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-computes-on)