CVE-2023-52137Public exploitNetwork attack vector

Runner code execution via unsanitized filename output

Published Dec 29, 2023 · Updated Aug 2, 2024

Command injection in tj-actions verify-changed-files before 17.0.0 allows remote authenticated users to execute code through changed filenames. The action exposes unsanitized changed-file names as workflow outputs, so direct expression interpolation into a Bash run block treats shell metacharacters as commands. Exploitation requires control of a changed filename and a consuming workflow that interpolates the output directly; commands run with the GitHub runner's permissions and can read available secrets.

CVSS severity7.7
High
EPSS probability2.62%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Command injection in tj-actions verify-changed-files before 17.0.0 allows remote authenticated users to execute code through changed filenames. The action exposes unsanitized changed-file names as workflow outputs, so direct expression interpolation into a Bash run block treats shell metacharacters as commands. Exploitation requires control of a changed filename and a consuming workflow that interpolates the output directly; commands run with the GitHub runner's permissions and can read available secrets.

The record

CVE
CVE-2023-52137
Published
Dec 29, 2023
Updated
Aug 2, 2024
Vendor
tj-actions
Product
verify-changed-files
Classifications
CWE-77, CWE-20, T1059.004
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Dec 29, 2023CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 17.0.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

tj-actions · verify-changed-filesversion=< 17.0.0

Published CVSS scores

7.7GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L
8.8NIST National Vulnerability DatabaseCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection')
CWE-20Improper Input Validation
T1059.004Command and Scripting Interpreter: Unix Shell

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo