Chaintj-actions · branch-namesGitHub Actions:tj-actions/branch-names
tj-actions branch-names: related fixes (2023–2025)
3 CVEs over 2 generations, 4 Dec 2023 to 26 Jul 2025.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2023-492914 Dec 2023 First in the chain
- CVE-2023-5166427 Dec 2023 No direct link to an earlier CVE
- CVE-2025-5441626 Jul 2025 related to CVE-2023-49291related to CVE-2023-51664
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2023-49291 | 4 Dec 2023 | Improper Sanitization of Branch Name Leads to Arbitrary Code Injection | First in chain | 21.2 |
| CVE-2023-51664 | 27 Dec 2023 | tj-actions/changed-files command injection in output filenames | First in chain | 22.8 |
| CVE-2025-54416 | 26 Jul 2025 | tj-actions/branch-names Contains Command Injection Vulnerability | CVE-2023-49291 · related · High | 21.8 |