CVE-2026-117624

Description

A flaw was found in Jenkins. The application fails to consistently enforce restrictions against deserializing certain object types as nested values when those types are designated only for top-level configuration files. An attacker can exploit this flaw by submitting crafted configuration data to bypass root element validation checks and potentially inject unauthorized nested objects into the system.

Statement

Red Hat Product Security rates this vulnerability as Moderate severity because an attacker must already possess valid authentication and specific configuration rights, restricting the blast radius to unauthorized nested settings modification rather than complete system takeover. In Red Hat OpenShift and enterprise environments utilizing Jenkins, standard deployments enforce role-based access controls that restrict configuration capabilities to trusted team members. Consequently, unprivileged or unauthenticated users cannot trigger this deserialization flaw under typical operational settings.

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Application Data; Unexpected State

Attackers can modify unexpected objects or data that was assumed to be safe from modification. Deserialized data or code could be modified without using the provided accessor functions, or unexpected functions could be invoked.

Availability

Technical Impact: DoS: Resource Consumption (CPU)

If a function is making an assumption on when to terminate, based on a sentry in a string, it could easily never terminate.

Other

Technical Impact: Varies by Context

The consequences can vary widely, because it depends on which objects or methods are being deserialized, and how they are used. Making an assumption that the code in the deserialized object is valid is dangerous and can enable exploitation. One example is attackers using gadget chains to perform unauthorized actions, such as generating a shell.

Frequently Asked Questions

Want to get errata notifications? Sign up here.