dbcve.org
EigentApplication

CVE-2026-22869

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 0.0.78 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The CI workflow in .github/workflows/ci.yml uses the pull_request_target trigger combined with checkout of untrusted PR code, allowing arbitrary code execution from fork pull requests with repository write permissions. Attackers can steal credentials, post comments, push code, or create releases.

MitigationReplace pull_request_target with pull_request trigger, or remove the checkout of untrusted PR code, or use sparse-checkout with explicit trusted paths, and ensure GITHUB_TOKEN has minimal permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EigentApplication
Affected:< 0.0.78

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the CI workflow file
    Find and open .github/workflows/ci.yml in the repository
    Affected if The file exists and contains a pull_request_target trigger with checkout of untrusted PR code
  2. Verify pull_request_target trigger is used
    Search the workflow file for 'pull_request_target' in the 'on:' section
    Affected if The workflow uses pull_request_target instead of pull_request
  3. Confirm untrusted code checkout occurs
    Look for 'actions/checkout' step in the workflow that runs on pull_request_target events without path restrictions
    Affected if The workflow checks out PR code without using sparse-checkout with explicit trusted paths or other restrictions
  4. Check GITHUB_TOKEN permissions
    Inspect if the workflow requests write permissions or uses default token scope without explicit permissions limiting
    Affected if The GITHUB_TOKEN has elevated permissions (write access) enabling the attacker to perform privileged actions

A user is affected if their repository contains .github/workflows/ci.yml using pull_request_target with an unrestricted checkout of untrusted PR code and elevated token permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.0.78 or later
Fixed in 0.0.78
Vendor patch github.com →
Interim mitigation

Replace pull_request_target with pull_request trigger, or remove the checkout of untrusted PR code, or use sparse-checkout with explicit trusted paths, and ensure GITHUB_TOKEN has minimal permissions.

Recommended fix High confidence

0.0.78

  1. Update the Eigent dependency to version 0.0.78 or later using your package manager (e.g., pip install eigent==0.0.78, npm install [email protected], or equivalent)
  2. If you have a custom .github/workflows/ci.yml file, fetch the updated version from the repository after upgrading, or manually apply the fix from commit bf02500bbbab0f01cd0ed8e6dc21fe5683d6bfb5 which changes the workflow to avoid pull_request_target with untrusted checkout
  3. Verify the CI workflow no longer uses pull_request_target with checkout of untrusted PR code, or uses appropriate safeguards like path filtering, workflow dispatch restrictions, or the recently fixed implementation
  4. Re-run any affected CI pipelines to ensure the fix is applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Eigent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22869 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22869 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data