AI Science Tracker

GHSL AI-agent index lists fork-artifact poisoning in SPIFFE SPIRE reviewer workflow

spiffe/spire GitHub Actions assign-reviewer-review-apply workflow · AI involvement attributed to GitHub Security Lab AI agent (system not named in advisory)

Finding and attribution

An artifact produced by a fork-controlled workflow can overwrite a trusted JavaScript helper in the privileged consumer workspace; the consumer imports and executes that helper before validating artifact data.

Product: spiffe/spire GitHub Actions assign-reviewer-review-apply workflow. AI system: GitHub Security Lab AI agent (system not named in advisory). Team / organization: GitHub Security Lab.

CVE identifiers: Not established in the cited evidence.

AI and human contribution (source account): GHSL’s primary AI-agent index lists this advisory among findings discovered with AI agents. The item advisory credits Jaroslav Lobačevski but does not name an AI system or detail agent involvement; attribution is index-level only.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The report describes an attack path and remediation; no exploitation in the wild is claimed.

Remediation status: fix documented. A fix pull request was merged 2026-09-04. The advisory notes that fork workflow approval policy may be required, but no approving review is needed in the described pull-request path.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 16 Sep 2026. AI attribution dated 16 Sep 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Not available · no assessment established here. Documented technical effects: code execution.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

No source-backed CVSS assessment is established in this catalog.

Case-level evidence: code execution.
Prerequisites / affected scope: Attacker-controlled fork artifact is extracted into a trusted-code workspace; source describes replacement of executable workflow code..
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: A fix pull request was merged 2026-09-04. The advisory notes that fork workflow approval policy may be required, but no approving review is needed in the described pull-request path.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases