Quick answers
- Is CVE-2026-18287 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18287 being exploited in the wild.
- How severe is CVE-2026-18287?
- High severity, with a CVSS score of 7.8, published 20 August 2026.
- Which products and versions are affected?
- Aeon Aeon.
- Is there a fix for CVE-2026-18287?
- A patch was published on 2026-07-29: Patch released via GitHub commit 7519180 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18287 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-18287?
- Check whether you run Aeon. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the load_time_series_segmentation_benchmark method due to insufficient validation of user-supplied input before it is passed to Python code execution. The flaw is a code injection vulnerability that allows an attacker to inject arbitrary Python code. Exploitation requires user interaction—the target must open a malicious file or visit a malicious web page. The attack vector is local with user interaction required. An attacker can execute code in the context of the current process, potentially leading to full system compromise. A patch has been released by the vendor (commit 7519180).
Affected products
- Aeon Aeon
Timeline
- 2026-02-19: disclosed: Vulnerability reported to vendor
- 2026-07-29: advisory: Coordinated public release of advisory (ZDI-26-470)
- 2026-07-29: patched: Patch released via GitHub commit 7519180