CVE-2025-53104
Published: 01 July 2025
Summary
CVE-2025-53104 is a critical-severity Command Injection (CWE-77) vulnerability. Its CVSS base score is 9.1 (Critical).
Operationally, ranked in the top 19.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2025-53104 is a command injection vulnerability (CWE-77) affecting the discussion-to-slack.yml GitHub Actions workflow in the gluestack-ui library, a collection of Tailwind CSS components, prior to commit e6b4271. Untrusted fields from GitHub Discussions, including title and body, were directly interpolated into shell commands inside a run block without sanitization.
An unauthenticated attacker can exploit the flaw by posting a crafted GitHub Discussion containing shell metacharacters or command substitutions, resulting in arbitrary command execution on the workflow runner and potential disclosure or modification of repository secrets and artifacts.
The referenced GitHub security advisory GHSA-432r-9455-7f9x and the fixing commit state that the workflow was removed entirely to address the issue; downstream users are instructed to delete discussion-to-slack.yml from any forks or derivatives of the repository.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-19665
Vulnerability details
gluestack-ui is a library of copy-pasteable components & patterns crafted with Tailwind CSS (NativeWind). Prior to commit e6b4271, a command injection vulnerability was discovered in the discussion-to-slack.yml GitHub Actions workflow. Untrusted discussion fields (title, body, etc.) were directly interpolated into…
more
shell commands in a run: block. An attacker could craft a malicious GitHub Discussion title or body (e.g., $(curl ...)) to execute arbitrary shell commands on the Actions runner. This issue has been fixed in commit e6b4271 where the discussion-to-slack.yml workflow was removed. Users should remove the discussion-to-slack.yml workflow if using a fork or derivative of this repository.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
No mitigating controls mapped yet. The per-CVE control annotator has not reached this CVE.