Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker crafts malicious CSV with injected Python
-
DeliveryDelivers file as fake benchmark dataset
-
ExploitUser loads file via aeon API call
-
Execution`eval()` executes injected expression
-
ImpactArbitrary code runs as current user process
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target user is running aeon version 1.3.0 and directly invokes |
| Impact | The CVSS 3.0 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects full confidentiality, integrity, and availability impact within the process scope, contingent on user interaction. EPSS data is not provided; given the niche deployment footprint and the requirement for deliberate file loading by a data science user, real-world mass exploitation probability is low despite the high CVSS. There is no CISA KEV listing and no public exploit code at time of analysis. The vulnerability is not remotely exploitable in a server context - it requires a human to invoke the vulnerable function on an attacker-supplied file, making automated scanning or worm-style propagation infeasible. The primary real-world risk is targeted supply-chain or social engineering attacks against ML researchers or data scientists who work with external time series benchmark datasets. The secondary |
| Exploit ScenarioDerived | An attacker crafts a malicious CSV benchmark dataset where one of the numpy array columns contains an injected Python expression such as |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 20, 2026
Arbitrary code execution in aeon 1.3.0 is triggered when a user loads a maliciously crafted CSV dataset file via the load_time_series_segmentation_benchmark or load_human_activity_segmentation_datasets functions, both of which passed CSV column values directly to Python's eval() built-in without validation. An attacker who convinces a data scientist or researcher to open a crafted dataset file can execute arbitrary Python code with the privileges of the running process. No public exploit has been identified at time of analysis, but the upstream fix commit is public and the vulnerability class is trivially replicable given the use of bare eval().
RemediationAI
The upstream fix is available in commit 751918052c0cce266b4f7cd4b084408526efc015 at https://github.com/aeon-toolkit/aeon/commit/751918052c0cce266b4f7cd4b084408526efc015; a released patched version beyond 1.3.0 is not independently confirmed from the available data - monitor the aeon PyPI page and GitHub releases for a tagged fix release and upgrade as soon as one is available. As a workaround prior to patching, avoid loading CSV dataset files from untrusted or external sources via load_time_series_segmentation_benchmark or load_human_activity_segmentation_datasets. In pipeline or CI contexts, restrict dataset ingestion to files from verified internal sources only. If aeon cannot be upgraded immediately, patching _tss_data_loaders.py locally to replace eval(val) with ast.literal_eval(val) inside a try/except reproduces the upstream fix with no functional trade-offs for well-formed datasets.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-94 (Improper Control of Generation of Code), specifically the use of Python's eval() built-in to deserialize numpy array literals stored in CSV columns (np_cols) within aeon/datasets/_tss_data_loaders.py. Because eval() executes arbitrary Python expressions - not merely literals - any attacker-controlled string in those CSV columns becomes executable code. The fix replaces eval() with ast.literal_eval(), which is restricted to safe Python literals (strings, numbers, lists, tuples, dicts, booleans, None) and raises a ValueError on anything more complex. A secondary fix in aeon/datasets/rehabpile_loader.py removes np.load(..., allow_pickle=True), eliminating a distinct pickle deserialization vector in the same dataset loading subsystem. Affected product is CPE cpe:2.3:a:aeon:aeon:*:*:*:*:*:*:*:*, specifically confirmed at version 1.3.0 per EUVD-2026-63435.
Know when Aeon gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
File-based attack requires local file loading with user interaction (UI:R, AV:L); no authentication needed to craft the malicious CSV (PR:N); full process-level impact (C:H/I:H/A:H).
Primary rating from Vendor (zdi).
CVSS VectorVendor: zdi
DescriptionCVE.org
Aeon load_time_series_segmentation_benchmark Code Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of aeon. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the load_time_series_segmentation_benchmark method. The issue results from the lack of proper validation of a user-supplied string before using it to execute Python code. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-29159.
Articles & Coverage 1
Executive ViewAI
aeon 1.3.0 contains an arbitrary code execution vulnerability in its CSV data loading functions that allows attackers to execute arbitrary Python code when researchers load crafted dataset files, potentially compromising research systems and intellectual property. This vulnerability poses significant risk to data science teams lacking immediate compensating controls.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict CSV loading to air-gapped or sandboxed environments with limited system access; (2) Disable load_time_series_segmentation_benchmark and load_human_activity_segmentation_datasets functions where operationally feasible; (3) Enforce mandatory code review and validation of all externally-sourced CSV files before import; (4) Require documented provenance for all datasets and limit imports to internal, pre-vetted repositories; (5) Implement runtime monitoring for unexpected code execution patterns from aeon processes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Remote code execution in Aeon 1.3.0 is triggered when a user loads a maliciously crafted dataset file via the load_rehab
Remote code execution in aeon 1.3.0 is possible when a user loads a maliciously crafted CSV dataset via the `load_human_
WAON "Service Application" for Android 1.4.1 and earlier does not verify SSL certificates. Rated medium severity (CVSS 5
Multiple cross-site scripting (XSS) vulnerabilities in Atlas Systems Aeon 3.5 and 3.6 allow remote attackers to inject a
EUVD-2026-63435
GHSA-qvfj-hqjq-cmgm
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB