{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-53104 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53104 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53104 is a critical command injection vulnerability in gluestack-ui, published on 1 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53104 and fix it if it is affected.\n\nWhat it is: CVE-2025-53104 is a critical command injection vulnerability in gluestack-ui, published on 1 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-53104 in the wild and no public exploit code.\n\nAffected product: gluestack-ui. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-53104/ (Markdown: https://insights.sbomify.com/CVE-2025-53104/index.md)","id":"CVE-2025-53104","markdown":"https://insights.sbomify.com/CVE-2025-53104/index.md","name":"CVE-2025-53104","record":{"aliases":["GHSA-432r-9455-7f9x"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions workflow","requires_auth":"none","summary":"Attackers can execute arbitrary shell commands on GitHub Actions runners by injecting malicious code into discussion titles or bodies.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"gluestack-ui is a library of copy-pasteable components \u0026 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-04","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-04T04:35:52Z","kind":"github_poc","ref":"https://github.com/pvharmo2/gha-lab-3b0a828a69","stars":0,"title":"Security-research lab reproducing CVE-2025-53104 (GHSA-432r-9455-7f9x): command injection in discussion-to-slack.yml of gluestack/gluestack-ui"}],"tier":"poc_unverified"},"has_fix":false,"headline":"gluestack-ui Command Injection Vulnerability via discussion-to-slack GitHub Action Workflow","id":"CVE-2025-53104","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"GLPI permits unauthorized rules execution order","id":"CVE-2025-53105"},"packages":[],"prev":{"headline":"JUnit OpenTestReportGeneratingListener can leak Git credentials","id":"CVE-2025-53103"},"products":["gluestack-ui"],"published":"2025-07-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-07-01","vendors":["gluestack"]},"summary":"Attackers can execute arbitrary shell commands on GitHub Actions runners by injecting malicious code into discussion titles or bodies.","url":"https://insights.sbomify.com/CVE-2025-53104/"}