CVE-2023-51664

What it is

tj-actions/changed-files is a Github action to retrieve all files and directories. Prior to 41.0.0, the `tj-actions/changed-files` workflow allows for command injection in changed filenames, allowing an attacker to execute arbitrary code and potentially leak secrets. This issue may lead to arbitrary command execution in the GitHub Runner. This vulnerability has been addressed in version 41.0.0. Users are advised to upgrade.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. High risk of data exposure, data tampering.

Exploit odds

3.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-12-27 17:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 06:41 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 3.4% in the next 30 days (EPSS).
• Severity: 7.3 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-12-27 17:15 UTC

Last modified

2026-06-17 06:41 UTC

Exploit probability

3.4% · EPSS, next 30 days

Weakness

CWE-74

Record status

Modified

Affected

• tj-actions changed-files < 41.0.0

Attack profile CVSS 3.1 · 7.3

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2023-51664.md and follow it. Check whether this project is affected by CVE-2023-51664. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge