CVE-2025-53104
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2025-07-01

Last updated on: 2025-07-03

Assigner: GitHub, Inc.

Description
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 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-07-01
Last Modified
2025-07-03
Generated
2026-05-06
AI Q&A
2025-07-01
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-77 The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a command injection issue in the discussion-to-slack.yml GitHub Actions workflow of the gluestack-ui library. Untrusted input from GitHub Discussion fields like title or body was directly inserted into shell commands without proper sanitization. An attacker could craft a malicious discussion title or body containing shell commands (e.g., $(curl ...)) that would be executed on the GitHub Actions runner, potentially allowing arbitrary command execution. The vulnerability was fixed by removing the vulnerable workflow.


How can this vulnerability impact me? :

If exploited, this vulnerability allows an attacker to execute arbitrary shell commands on the GitHub Actions runner where the workflow is executed. This could lead to unauthorized access, data leakage, or manipulation of the build environment, potentially compromising the security and integrity of the CI/CD pipeline.


What immediate steps should I take to mitigate this vulnerability?

Remove the discussion-to-slack.yml GitHub Actions workflow from your repository or fork, as the vulnerability is due to untrusted discussion fields being interpolated into shell commands in this workflow. This workflow was removed in commit e6b4271, which fixes the issue.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart