CVE-2026-31228: The Adversarial Robustness Toolbox (ART) thru 1.20.1 contains a remote code execution vulnerability in its...
The Adversarial Robustness Toolbox (ART) thru 1.20.1 contains a remote code execution vulnerability in its Kubeflow component. The robustness evaluation function for PyTorch models uses the unsafe eval() function to dynamically evaluate user-supplied strings for the LossFn and Optimizer parameters without any sanitization or security restrictions. An attacker can exploit this by providing a specially crafted string that contains arbitrary Python code, which will be executed when eval() is called, leading to complete compromise of the system running the ART evaluation.
Security readout for executives and security teams
Plain-English summary
CVE-2026-31228 is a critical remote code execution issue in the Kubeflow component of Adversarial Robustness Toolbox through 1.20.1. If an attacker can control model-evaluation parameters, their input may run as Python code on the evaluation host, risking full system compromise.
Executive priority
Prioritize urgently for organizations running shared or externally triggered ML evaluation pipelines. A successful attack could turn a model-evaluation job into system-level compromise. If ART is not deployed, business urgency is low but still track dependency exposure.
Technical view
The PyTorch robustness evaluation path reportedly calls Python eval() on user-supplied LossFn and Optimizer strings without sanitization or restrictions. This is CWE-94 code injection with CVSS 9.8, network attack vector, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in ML, MLOps, or Kubeflow environments using adversarial-robustness-toolbox through 1.20.1 and accepting untrusted or externally influenced evaluation parameters. The source bundle does not identify specific vendor packages, distributions, or CPEs.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. The risk is still severe because the described flaw needs no privileges or user interaction when the vulnerable evaluation interface is reachable.
Researcher notes
Evidence is clear on the vulnerable pattern and impact, but incomplete on fixed versions, exploit sightings, and packaged product mapping. Treat affected scope as ART through 1.20.1 only where the described Kubeflow PyTorch evaluation path is used.
Mitigation direction
Inventory ART usage, especially Kubeflow PyTorch robustness evaluation workflows.
Stop accepting untrusted LossFn or Optimizer parameter strings.
Isolate or disable affected evaluation jobs until vendor guidance is confirmed.
Check Trusted-AI, CVE, and Red Hat advisories for patched versions or official mitigations.
Restrict network access to ML evaluation services and pipeline submission interfaces.
Validation and detection
Identify installed adversarial-robustness-toolbox versions and flag through 1.20.1.
Review Kubeflow pipelines for PyTorch robustness evaluation use.
Check whether LossFn or Optimizer values can originate from users, APIs, or files.
Confirm runtime isolation and least privilege for evaluation workers.
Monitor advisory sources for updated affected-product and remediation details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.