CVE-2023-51664
A public proof of concept exists; no exploitation attested.
- Published2023-12-27
- Fixed in41
- WeaknessCWE-74 · CWE-77
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2023-12-2717:15CVE publishedNVD
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 41.x | < 41 | 41 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 41.0 | < 41.0.0 | 41.0.0 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- tj-actions changed-filesAffected
- = < 41.0.0no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-12-27
Fix
- Update tj-actions/changed-files to 41
Advisories and patches
- github.comPatch
- github.comPatch
- github.comPatch
- github.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2024-09-25
- PoC-in-GitHubno public repository identifiedread 2026-11-08
- Metasploit modules
- none listed Metasploit Framework
Sources
- CISA-ADPSSVC decisionpoc2024-09-25
- CNACVSS 3.17.3known since 2026-10-23
- NVDCVSS 3.19.8read 2026-10-23
- CNAweakness (CWE)CWE-74, CWE-77known since 2026-10-23
- NVDweakness (CWE)CWE-77read 2026-10-23
- FIRST EPSSEPSS score3.4 %2026-11-08
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2024-01-02
Identifiers
- EUVD-2024-0385same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-mcph-m25j-8j63same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2023-12-27
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-mcph-m25j-8j63
Frequently asked questions
What is CVE-2023-51664?
Is CVE-2023-51664 actively exploited?
What is the CVSS score for CVE-2023-51664?
Running tj-actions/changed-files? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-mcph-m25j-8j63
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0