Eigent CI Workflow Remote Code Execution via pull_request_target Misconfiguration (CVE-2026-22869)
Executive & SecOps Summary
SECOPS ASSESSMENTThe .github/workflows/ci.yml workflow configuration in the Eigent open-source repository
Arbitrary code execution from fork pull requests, allowing attackers to steal credentials, push unauthorized code, or create malicious releases
Apply the official patch commits or update the GitHub Actions workflow configuration to restrict untrusted code execution
Affected Products & Version Scope
Remediation & Live Workaround Commands
PATCH & WORKAROUND1. Official Patch & Version Upgrade Commands
Update your repository to include the official security patches or pull the latest main branch containing the fix.
# Fetch and merge the latest secure main branch
git fetch origin
git checkout main
git pull
# Verify the application of the patch commit (bf02500bbbab0f01cd0ed8e6dc21fe5683d6bfb5)
git show bf02500bbbab0f01cd0ed8e6dc21fe5683d6bfb52. Temporary Workaround & Hardening Configuration
If you cannot immediately update, modify .github/workflows/ci.yml to replace pull_request_target with the safer pull_request trigger, or ensure untrusted code is not checked out with write permissions.
# Example of hardening .github/workflows/ci.yml
on:
# Use pull_request instead of pull_request_target to isolate execution
pull_request:
branches: [ 'main' ]
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v43. Log Audit & IoC Verification Commands
Audit your GitHub Actions run history to identify unauthorized or suspicious workflow executions triggered by external pull requests.
# List recent workflow runs triggered by pull_request_target using GitHub CLI
gh run list --workflow=ci.yml --event=pull_request_target --limit 20
# Inspect logs of a specific run for suspicious outbound connections or credential access
# gh run view <run-id> --logScan Your Repositories for Transitive Vulnerable Dependencies in 30 Seconds
Automatically detect vulnerable packages across npm, PyPI, Maven, and Go, and open automated fix Pull Requests without breaking your build.
Technical Root Cause & Exploitation Mechanics
1. Vulnerability Overview & Root Cause
A critical security vulnerability exists in the CI workflow (.github/workflows/ci.yml) of Eigent, a multi-agent Workforce platform. The root cause lies in the insecure combination of the pull_request_target trigger and checking out untrusted code from fork pull requests. Because pull_request_target runs in the context of the base repository, it has access to write permissions and repository secrets, making it highly dangerous when combined with untrusted code execution.
2. Exploitation Mechanics & Attack Scenario
An attacker forks the Eigent repository, injects malicious commands into the codebase (such as build scripts or tests), and submits a pull request. When the PR is submitted, the pull_request_target event triggers the CI workflow in the parent repository. The workflow checks out the untrusted code from the fork and executes it. Since the runner executes with the parent repository's write-access GITHUB_TOKEN and secrets, the attacker's payload runs with elevated privileges.
3. Infrastructure & Business Impact
Successful exploitation allows attackers to compromise the repository's integrity. Attackers can exfiltrate sensitive credentials, push unauthorized code directly to the repository, post malicious comments, or create rogue releases. This poses a severe supply chain risk to downstream users and deployments relying on the Eigent platform.
Official Vendor Advisories & References
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.
Frequently Asked SecOps Questions (CVE-2026-22869)
FAQQ1. How critical is CVE-2026-22869 and is it actively exploited in the wild?
CVE-2026-22869 is rated CVSS 9.8 (CRITICAL) with a 30-day EPSS exploitation probability of 0.6%. Organizations running affected versions should prioritize patching based on network exposure.
Q2. Which vendors and products are affected by CVE-2026-22869?
Primary impacted vendors include eigent-ai across eigent. Scope summary: Eigent open-source repository versions prior to the security patch in .github/workflows/ci.yml
Q3. What temporary mitigations or workarounds exist for CVE-2026-22869 before patching?
[Mitigation] Apply the official patch commits or update the GitHub Actions workflow configuration to restrict untrusted code execution Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.
Generate an Internal Engineering Notice or CISO Report for CVE-2026-22869
Instantly format this advisory into an executive CISO summary or engineering patch ticket.
🔗 Related Advisories in Similar Stack (eigent-ai)
View Category →Gitea Remote Code Execution Vulnerability via diffpatch API and Git Hooks (CVE-2026-60004)
[Affected Scope] Gitea versions prior to 1.27.1
PostyBirb Plus Cross-Site Scripting (XSS) Vulnerability (CVE-2026-120190) Security Advisory
[Affected Scope] PostyBirb Plus versions up to and including 3.1.75
GitLab CE/EE Unauthenticated Remote Code Execution (RCE) Advisory (CVE-2026-97229)
[Affected Scope] GitLab CE/EE versions 19.2 (< 19.2.8), 19.3 (< 19.3.5), and 19.4 (< 19.4.2)
GitLab CE/EE Unauthenticated Arbitrary File Read Vulnerability (CVE-2026-85706)
[Affected Scope] GitLab CE/EE versions from 18.7 through 19.3.1.
Subscribe to Daily Vulnerability Briefings & KEV Alerts
Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.