Finding and attribution
The migrator.yml workflow interpolates a pull request comment body into JavaScript in a privileged GitHub Actions context, risking command execution and secret exposure.
Product: ansys/pymapdl. 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): GHSL credits CodeQL and its AI agent and reports the finding to Ansys on 2025-08-04; the maintainer fixed it 2025-08-05. The source does not isolate which contributor identified it 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 public advisory documents the vulnerability and disclosure/remediation status. It does not claim exploitation in the wild.
Remediation status: fix documented. Maintainer fixed the issue 2025-08-05. No CVE was established in this 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 2 Sep 2025. AI attribution dated 2 Sep 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, data disclosure, data modification.
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, data disclosure, data modification.
Prerequisites / affected scope: An issue commenter can trigger code injection in the privileged migrator workflow. The workflow has contents:write permission and uses sensitive secrets, including PYANSYS_CI_BOT_TOKEN..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: Maintainer fixed the issue 2025-08-05. No CVE was established in this advisory.