CVE-2026-22869: eigent · Code Injection
Affects eigentSource CVE Database V5
Public exploit available · CVSS 8.9 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| eigent-aieigent | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, organizations should immediately review and update their eigent CI workflows to avoid using the pull_request_target trigger when checking out code from untrusted forks. Instead, use the pull_request trigger, which runs workflows with the permissions of the contributor, limiting exposure. Restrict access to repository secrets by configuring GitHub Actions to not expose secrets to workflows triggered by forked pull requests. Implement strict permission boundaries in workflows, such as least privilege principles for tokens and credentials. Consider using GitHub's built-in security features like required reviews and branch protection rules to limit who can merge code. Regularly audit CI/CD configurations for insecure patterns and keep eigent updated to versions beyond bf02500bbbab0f01cd0ed8e6dc21fe5683d6bfb5 once patches are available. Additionally, monitor CI logs for suspicious activity and employ runtime detection for anomalous behavior during builds. Educate developers and DevOps teams on secure CI practices to prevent similar misconfigurations.
Description
Eigent is a multi-agent Workforce. A critical security vulnerability in the CI workflow (.github/workflows/ci.yml) allows arbitrary code execution from fork pull requests with repository write permissions. The vulnerable workflow uses pull_request_target trigger combined with checkout of untrusted PR code. An attacker can exploit this to steal credentials, post comments, push code, or create releases.