Finding and attribution
YDB’s validate-pr-description GitHub Actions workflow interpolates pull request-controlled text into a shell command in a privileged pull_request_target job, creating code injection risk.
Product: YDB. AI system: GitHub Security Lab AI agent and CodeQL. Team / organization: GitHub Security Lab.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): The GHSL advisory credits both CodeQL and an AI agent developed by GitHub Security Lab. Reported 2025-08-04; maintainers confirmed a fix on 2025-08-17. This attribution does not establish which contribution found the flaw first.
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 documents the finding and its disclosure/remediation state. It does not claim exploitation in the wild.
Remediation status: fix documented. Maintainer reported the fix in PR 22458 on 2025-08-17. No CVE was established in the advisory.
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 21 Aug 2025. AI attribution dated 21 Aug 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 labels execution in a privileged workflow context..
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: Maintainer reported the fix in PR 22458 on 2025-08-17. No CVE was established in the advisory.