aeon: Code execution via privileged GitHub Actions workflow
Summary
aeon, a scikit-learn compatible Python library for time series, had a GitHub Actions workflow that used the pull_request_target trigger for pre-commit checks. Code from a fork pull request could run in a privileged context with elevated credentials and could push commits to pull request branches. An attacker who submits a malicious fork pull request could expose the token and gain a write path to the repository. The flaw is in the project's own CI configuration and does not affect a typical installation of the library.
Affected
- aeon versions before 1.5.0 (CI workflow of the aeon repository)
Fixed in
- Fixed in aeon 1.5.0
Workaround
Unknown. No workaround is documented. Upgrading to 1.5.0 is the fix.
Exploitation
- No public exploit or in-the-wild exploitation known at the time of publication.
- Not listed in CISA KEV.
Our recommendation
- Upgrade aeon to version 1.5.0 or later in all projects and environments that use it.
- If your organisation maintains forks of aeon or its own GitHub Actions workflows, check for use of pull_request_target and avoid running untrusted pull request code with write access or secrets.
- Monitor the vendor advisory for updates.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- GitHub Security Advisory GHSA-mhg2-mc45-wrjr github.com
- Fix commit 99261e1 in aeon repository github.com
- Pull request #3394 in aeon repository github.com
- CVE-2026-65820 summary (threatint) cve.threatint.com
- OffSeq threat radar entry for CVE-2026-65820 radar.offseq.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 11 Nov 2026, 19:23.
Original description (NVD)
aeon is a scikit-learn compatible Python library for learning from time series. Prior to version 1.5.0, a GitHub Actions workflow used pull_request_target for pre-commit checks on pull requests from forks. In this configuration, fork-controlled code could be checked out and executed in a privileged context. The vulnerable workflow also generated/used elevated credentials and could automatically commit or push fixes back to pull request branches. This created a potential token exposure and repository write path if an attacker submitted a malicious fork pull request designed to execute during the privileged workflow run. This issue has been patched in version 1.5.0.
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.