CVE-2026-31229
Description
A flaw was found in the Adversarial Robustness Toolbox (ART), specifically within its Kubeflow component. This vulnerability, categorized as insecure deserialization (CWE-502), occurs when loading model weights without proper security restrictions. A remote attacker can exploit this by uploading a maliciously crafted model file or by controlling a parameter to point to such a file. Successful exploitation allows for the execution of arbitrary code on the affected system, leading to remote code execution.
Statement
Important: This flaw is not present in Red Hat products as the vulnerable code is not in the execution path. The Adversarial Robustness Toolbox (ART) Kubeflow component contains an insecure deserialization vulnerability that could lead to remote code execution through maliciously crafted model files. However, Red Hat OpenShift AI (RHOAI) components are not affected because the vulnerable code is not executed in their deployment.
Mitigation
To mitigate this issue, restrict access to object storage locations used by Kubeflow pipelines to trusted sources only. Implement strict validation and integrity checks for all model files before they are loaded into the Adversarial Robustness Toolbox within a Kubeflow environment. Ensure that only models from verified and trusted origins are processed. This reduces the risk of an attacker introducing a maliciously crafted model file.
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 | 8.8 | N/A | 9.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
