CVE-2026-65820 · Package
NO FIX YET · SEE WHAT TO DO
The aeon Python library's pre-commit GitHub Actions workflow ran code from forked pull requests in a privileged context. A malicious fork pull request could expose elevated credentials and push commits to the repository.
first public Jul 3, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
The flaw is in aeon's own CI workflow, not in the library code that applications import, so exposure is limited to people who run that workflow or a fork of the repository with the vulnerable configuration. Teams that only install aeon from PyPI are not exposed through this workflow. Teams that copied the workflow into their own repositories should check it.
Not affected if library-only-use, version-1.5.0-or-later
Who cares aeon, github-actions, python
pip show aeon.github/workflows file in the aeon repository that uses pull_request_target for pre-commit checks, if you maintain a fork or copy of the project1.5.0 or lateraeon 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.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.