CVE-2026-70430
Description
A flaw was found in Jenkins. This vulnerability allows an attacker with Overall/Manage permission to instantiate arbitrary types of objects within the project naming strategy configuration. This includes types typically reserved for administrators, potentially leading to unauthorized configuration changes or other administrative actions within the Jenkins environment.
Statement
Red Hat ships Jenkins as part of OpenShift Developer Tools and Services (ocp-tools). This flaw allows a user holding the Overall/Manage permission, rather than full Overall/Administer privileges, to submit a crafted project naming strategy configuration that causes Jenkins to instantiate arbitrary configuration-related object types, including types intended for administrator-only configuration. This weakens the separation between the Overall/Manage and Overall/Administer permissions. Exploitation requires an authenticated user who already holds the Overall/Manage permission, which is not granted by default and is typically reserved for trusted operators, limiting the practical impact. Fixed upstream in Jenkins 2.576 (weekly) and LTS 2.568.2.
Mitigation
Restrict the Overall/Manage permission to fully trusted administrators only; avoid delegating it to users who should not have administrator-equivalent configuration access. Audit the existing project naming strategy configuration for unexpected object types. Upgrade to a Jenkins release containing the fix (2.576 or LTS 2.568.2) once available in the ocp-tools image.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 3.8 | N/A | 2.7 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | High | N/A | High |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | None |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
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
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
