Security readout for executives and security teams
Plain-English summary
CVE-2026-22869 affects the Eigent GitHub repository workflow, not necessarily the shipped application runtime. A malicious fork pull request could cause the project’s CI to run attacker-controlled code with repository-level write permissions. Business risk centers on source-code integrity, credential exposure, and unauthorized repository actions.
Executive priority
Treat as high priority for teams maintaining Eigent source or CI mirrors. The main concern is compromise of the development pipeline, which can affect code integrity and downstream trust. Prioritize workflow update, secret review, and audit of recent CI activity.
Technical view
The vulnerable .github/workflows/ci.yml used pull_request_target while checking out untrusted pull request code. That pattern can execute attacker-controlled code in a privileged GitHub Actions context. The advisory describes possible credential theft, comments, code pushes, and release creation. Affected versions are before commit bf02500bbbab0f01cd0ed8e6dc21fe5683d6bfb5.
Likely exposure
Exposure is likely limited to eigent-ai/eigent forks or deployments using the vulnerable CI workflow before the fixed commit. Organizations only consuming released Eigent artifacts may have lower direct exposure, but should assess supply-chain trust if they mirrored or modified the workflow.
Exploitation context
The CVE record says exploitation is possible through fork pull requests and requires no privileges or user interaction. There is no provided KEV listing and no cited source states active exploitation in the wild.
Researcher notes
The evidence identifies a CI misconfiguration class, CWE-94, with CVSS 4.0 score 8.9. Public sources name the fixed commit and related pull requests, but do not provide active exploitation evidence. Analysis should focus on GitHub Actions trust boundaries and repository audit trails.
Mitigation direction
- Update the repository workflow to commit bf02500bbbab0f01cd0ed8e6dc21fe5683d6bfb5 or later.
- Review GitHub advisory GHSA-gvh4-93cq-5xxp for vendor-specific guidance.
- Avoid privileged pull_request_target workflows that check out untrusted pull request code.
- Rotate repository secrets if the vulnerable workflow ran on untrusted pull requests.
Validation and detection
- Check whether .github/workflows/ci.yml used pull_request_target before the fixed commit.
- Confirm the repository includes commit bf02500bbbab0f01cd0ed8e6dc21fe5683d6bfb5 or equivalent workflow changes.
- Review GitHub Actions logs for untrusted fork pull request runs.
- Audit repository events for unexpected pushes, comments, releases, or secret access indicators.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22869 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.9 (4.0)
- Known Exploited
- No
- Published
Vector: 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:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.9HighVector: 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:P
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/eigent-ai/eigent/security/advisories/GHSA-gvh4-93cq-5xxpCVE reference · x_refsource_CONFIRM
- https://github.com/eigent-ai/eigent/pull/836CVE reference · x_refsource_MISC
- https://github.com/eigent-ai/eigent/pull/837CVE reference · x_refsource_MISC
- https://github.com/eigent-ai/eigent/commit/bf02500bbbab0f01cd0ed8e6dc21fe5683d6bfb5CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.