AI Science Tracker

GHSL AI agent helps find privileged workflow injection in ESPHome docs

ESPHome documentation GitHub Actions · AI involvement attributed to GitHub Security Lab AI agent

Finding and attribution

The component-image.yml issue_comment workflow interpolated an untrusted comment body in a privileged script context, allowing code execution and cache poisoning risk.

Product: ESPHome documentation GitHub Actions. AI system: GitHub Security Lab AI agent. Team / organization: GitHub Security Lab.

CVE identifiers: Not established in the cited evidence.

AI and human contribution (source account): GHSL explicitly credits its AI agent and CodeQL jointly; the advisory does not isolate their contributions. Reported 2025-08-08 and fixed 2025-11-10. No CVE is listed.

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 advisory describes potential impact and remediation; it does not claim exploitation in the wild.

Remediation status: fix documented. GHSL says the issue was fixed on 2025-11-10. It describes cache poisoning as a potential impact; no CVE is listed.

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 11 Dec 2025. AI attribution dated 11 Dec 2025. 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 workflow input; source says privileged-context execution..
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: GHSL says the issue was fixed on 2025-11-10. It describes cache poisoning as a potential impact; no CVE is listed.

Original evidence

Download this source record (JSON)

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