Downloading malicious GitHub Actions workflow artifact results in path traversal vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/U:Green · score source

EPSS

• CVE-2024-54132: 0.63% estimated exploitation activity in the next 30 days; percentile 50.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A security vulnerability has been identified in GitHub CLI that could create or overwrite files in unintended directories when users download a malicious GitHub Actions workflow artifact through gh run download. Details This vulnerability stems from a GitHub Actions workflow artifact named .. when downloaded using gh run download. The artifact name and --dir flag are used to determine the artifact’s download path. When the artifact is named .., the resulting files within the artifact are extracted exactly 1 directory higher than the specified --dir flag value. In 2.63.1, gh run download will not download artifacts named .. and . and instead exit with the following error message: Impact Successful exploitation heightens the risk of local path traversal attack vectors exactly 1 directory higher than intended. Remediation and Mitigation 1. Upgrade gh to 2.63.1 2. Implement additional validation to ensure artifact filenames do not contain potentially dangerous patterns, such as…

Published by the source

4 Dec 2024, 15:32 UTC

Last modified by the source

4 Dec 2024, 22:17 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2m9h-r57g-45pj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-54132

Advisory: Downloading malicious GitHub Actions workflow artifact results in path traversal vulnerability
IDs: CVE-2024-54132, GHSA-2m9h-r57g-45pj
Record: https://patchnext.com/advisories/cve-2024-54132 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/cli/cli/v2 2.63.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cli/cli/v2: affected < 2.63.1; fixed in 2.63.1
- Go github.com/cli/cli: affected <= 1.14.0

## Suggested inspection (read-only)
- Go github.com/cli/cli/v2: check the installed version with your package manager.
- Go github.com/cli/cli: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cli/cli/v2, github.com/cli/cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2m9h-r57g-45pj (GitHub-reviewed advisory GHSA-2m9h-r57g-45pj lists affected ranges: Go github.com/cli/cli/v2 >=0 =0 <=1.14.0)

Commands are suggestions: review each one before running it.