CVE-2026-31230: The Adversarial Robustness Toolbox (ART) thru 1.20.1 contains a command-line argument injection vulnerabili...
The Adversarial Robustness Toolbox (ART) thru 1.20.1 contains a command-line argument injection vulnerability in its Kubeflow component (robustness_evaluation_fgsm_pytorch.py). The script uses the unsafe eval() function to parse string values provided via the --clip_values and --input_shape command-line arguments. This allows an attacker to inject arbitrary Python code into these arguments, which will be executed when eval() is called. The vulnerability can be exploited remotely if an attacker can control these arguments (e.g., through pipeline configuration or automated scripts), leading to arbitrary code execution on the system running the ART evaluation.
Security readout for executives and security teams
Plain-English summary
ART through version 1.20.1 can execute malicious Python code when its Kubeflow evaluation script receives attacker-controlled values for specific arguments. Successful exploitation could compromise the confidentiality, integrity, and availability of the system running the evaluation. Remote risk depends on whether pipelines or automation allow untrusted users to control those arguments.
Executive priority
Treat as urgent where the affected Kubeflow workflow accepts externally influenced configuration. Prioritize exposure discovery and containment because successful exploitation could fully compromise the evaluation environment. Environments not invoking the script, or enforcing trusted-only arguments, have materially lower immediate risk but still require verification.
Technical view
The Kubeflow script robustness_evaluation_fgsm_pytorch.py passes --clip_values and --input_shape strings to Python eval(). Crafted values can therefore become executable Python code with the evaluation process's privileges. The supplied CVSS 3.1 score is 9.8. The bundle does not identify a fixed version.
Likely exposure
Exposure is most likely where ART through 1.20.1 runs this Kubeflow component and pipeline configuration, automation, APIs, or users can influence the two vulnerable arguments. Installing ART alone does not establish exploitability; the affected script and an attacker-controlled input path must be present.
Exploitation context
The source bundle describes conditional remote arbitrary code execution when an attacker controls the arguments. It does not establish that the script is directly network-accessible. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation.
Researcher notes
The core vulnerable sink, affected arguments, affected range, and impact are specified. Product metadata is incomplete, listing vendor and product as “n/a,” and no fixed release is named. Validate package identity, deployment reachability, input provenance, and process privileges before assigning operational exposure. Do not equate the network CVSS vector with an inherently exposed network service.
Mitigation direction
Identify deployments using ART through 1.20.1 and the affected Kubeflow evaluation script.
Prevent untrusted users and external inputs from controlling the vulnerable command-line arguments.
Suspend affected evaluation workflows where trustworthy argument control cannot be guaranteed.
Run necessary evaluations with minimal privileges and isolated access while awaiting confirmed remediation.
Check ART and relevant vendor guidance for an official fix or safe upgrade version.
Validation and detection
Inventory installed ART versions and locate workflows invoking the affected Kubeflow script.
Trace how --clip_values and --input_shape values enter each evaluation workflow.
Confirm only trusted, authenticated configuration sources can set those arguments.
Review evaluation hosts and pipeline logs for unexpected process behavior or configuration changes.
Verify any adopted release or mitigation against official project or vendor guidance.
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-88: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter 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.
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-88 · source CWE mapping
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.