CVE-2026-65820: aeon: Privileged GitHub Actions workflow allowed fork-controlled code execution
aeon is a scikit-learn compatible Python library for learning from time series. Prior to version 1.5.0, a GitHub Actions workflow used pullrequesttarget 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.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
aeonto a version that resolves this vulnerability.Fixed in 1.5.0
Event History
Frequently Asked Questions
Who is exposed to this issue?
The exposed party is the aeon repository and its GitHub Actions environment, particularly maintainers who run the affected workflow against pull requests submitted from forks. Users of the Python library are not described as directly affected by the workflow issue.
What does an attacker need to exploit it?
An attacker would need to submit a malicious pull request from a fork and have the vulnerable pre-commit workflow run on it. The workflow's pull_request_target configuration could then check out and execute attacker-controlled code with privileged workflow context.
Are default GitHub Actions permissions sufficient to create the risk?
The described risk depends on the workflow generating or using elevated credentials and having the ability to commit or push fixes back to pull request branches. The provided information does not establish whether a default GitHub Actions configuration alone is affected.
What should maintainers do if they cannot immediately upgrade?
Avoid running privileged pull_request_target workflows that check out or execute code supplied by fork pull requests. Remove or restrict elevated credentials and disable automated commits or pushes to pull request branches until the workflow can be updated.
How can maintainers determine whether they are affected?
Review GitHub Actions workflows for pull_request_target triggers used for pre-commit checks on fork pull requests, especially workflows that check out pull-request code. Prior to aeon 1.5.0, also check whether those workflows generate or use elevated credentials or automatically push changes to pull request branches.