Disclosed weakness · no CVE recorded
An agent-controlled artifact filename could alter the archive command
GitHub · GitHub Agentic Workflows · artifact upload
First documented disclosure · Review checkpoint
Summary
A workflow agent could influence the command that a more privileged artifact uploader ran.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: The issue reports a static analysis. The project sources identify no malicious use.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The upload action passed staged filenames to its archive utility without distinguishing them from command options.
Conditions required
An agent can name staged artifacts and the workflow uses the affected archive/upload path.
Potential impact
The original static analysis found a route to code execution in the upload job with its credentials.
Affected versions and configurations
The project identified the pre-fix artifact upload implementation. A vulnerable release range was not published.
Fix and mitigation status
PR 78015 on main. The weekly update identifies the change without naming a fixed release.
Practical next steps
Use a build containing PR 78015 and restrict upload-job credentials to the minimum required.
Operating lesson
Treat filenames crossing from an agent into a privileged job as untrusted data.
Evidence and limits
The November 15 issue is a static finding. The November 16 project update identifies the patch.
Sources
- GitHub Agentic Workflows original finding
Primary source ·
- GitHub artifact uploader patch
Primary source ·
- GitHub Agentic Workflows weekly update
Primary source ·