Arbitrary file write via unchecked artifact paths
Published Sep 2, 2024 · Updated Aug 27, 2025
Path traversal in GitHub Actions Toolkit 2.0.0 through 2.1.1 allows attackers to write files via crafted artifact entries. The downloadArtifactInternal, downloadArtifactPublic, and streamExtractExternal paths passed entry names to unzip-stream extraction without confining resolved paths to the destination directory. Exploitation requires a consuming workflow to extract an attacker-controlled artifact, after which traversal entries overwrite files writable by the runner process.
Summary
What happened
Path traversal in GitHub Actions Toolkit 2.0.0 through 2.1.1 allows attackers to write files via crafted artifact entries. The downloadArtifactInternal, downloadArtifactPublic, and streamExtractExternal paths passed entry names to unzip-stream extraction without confining resolved paths to the destination directory. Exploitation requires a consuming workflow to extract an attacker-controlled artifact, after which traversal entries overwrite files writable by the runner process.
The record
- CVE
- CVE-2024-42471
- Published
- Sep 2, 2024
- Updated
- Aug 27, 2025
- Vendor
- Product
- GitHub Actions Toolkit
- Classifications
- CWE-22, T1195.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 2, 2024CVE publishedPublication date reported by the CVE source.
- Aug 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.0.0, < 2.1.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo