CVE-2026-65820: aeon · Code Injection
Affects aeonSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 1.5.0 soon.
Data as of 11 Nov 2026, 18:07 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.7 |
|---|
- Patch
- Available – fixed in 1.5.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade aeon to 1.5.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| aeon-toolkitaeon | Affected
| Fixed in
|
AI-suggested
Upgrade aeon to version 1.5.0 or later, where the vulnerable GitHub Actions workflow configuration has been fixed. No additional mitigation is required once the upgrade is applied.
Description
A code injection vulnerability (CWE-94) exists in the aeon-toolkit aeon library prior to version 1.5.0. The issue arises from a GitHub Actions workflow using pull_request_target for pre-commit checks on forked pull requests, allowing malicious fork code to execute with elevated privileges. This could expose tokens and enable unauthorized repository write access. The vulnerability is fixed in version 1.5.0.