How severe is CVE-2024-42471?

CVE-2024-42471 has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2024-42471?

Affected package information for CVE-2024-42471 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2024-42471?

Apply the github actions toolkit security patch or hotfix for CVE-2024-42471 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2024-42471 across my infrastructure?

Inventory every github actions toolkit deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2024-42471 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2024-42471?

O3 detects and blocks CVE-2024-42471 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2024-42471 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-42471, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-42471?

CVE-2024-42471 has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-42471?

CVE-2024-42471 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2024-42471?

CVE-2024-42471 affects github actions toolkit; github actions\/artifact. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2024-42471 published, and has it been updated?

CVE-2024-42471 was published on September 2, 2024 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2024-42471

HIGH

actions/artifact is the GitHub ToolKit for developing GitHub Actions. Versions of `actions/artifact` on the 2.x branch before 2.1.2 are vulnerable to arbitrary file write when using…

Published

Sep 2, 2024

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk86th percentile-4.67%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

actions/artifact is the GitHub ToolKit for developing GitHub Actions. Versions of actions/artifact on the 2.x branch before 2.1.2 are vulnerable to arbitrary file write when using downloadArtifactInternal, downloadArtifactPublic, or streamExtractExternal for extracting a specifically crafted artifact that contains path traversal filenames. Users are advised to upgrade to version 2.1.2 or higher. There are no known workarounds for this issue.

Affected Products

2 products · 2 configurations

Application

actions toolkitgithub

all

Application

actions\/artifactgithub

≥ 2.0.0 && < 2.1.7

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52276localnodejs

unzip-stream 0.3.1 - Arbitrary File Write

by cybersploit · Apr 30, 2025

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every github actions toolkit deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the github actions toolkit security patch or hotfix for CVE-2024-42471 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2024-42471 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2024-42471. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

actions/artifact is the GitHub ToolKit for developing GitHub Actions. Versions of `actions/artifact` on the 2.x branch before 2.1.2 are vulnerable to arbitrary file write when using `downloadArtifactInternal`, `downloadArtifactPublic`, or `streamExtractExternal` for extracting a specifically crafted artifact that contains path traversal filenames. Users are advised to upgrade to version 2.1.2 or higher. There are no known workarounds for this issue.

O3 Security · Runtime Protection

Is CVE-2024-42471 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2024-42471 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works