> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/input-validation/appsec-cicd-186.md). # Workflow allows command execution through the standard output stream ## Rule Details | | | | --------------------- | ----------------- | | Cortex AppSec Rule ID | APPSEC\_CICD\_186 | | Category | Input Validation | | Severity | MEDIUM | ## Impact The ACTIONS\_ALLOW\_UNSECURE\_COMMANDS environment variable is set to 'True' in the GitHub Actions workflow. This setting, which was deprecated by GitHub, allows the workflow to evaluate the set-env and add-path commands once they have been written to the standard output stream. This can lead to command execution in the workflow. For example, a workflow that prints the title of new GitHub issues to the standard output stream, would allow an attacker to create a GitHub issue with a malicious title that would be evaluated by the workflow. Note: although this setting was deprecated by GitHub, it is still functional. For more information see: ## Recommended Solution - Buildtime Disable the use of unsecure commands in GitHub Actions workflows in one of the following two manners: * Set the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to **False**. * Delete the environment variable. **📌 NOTE**\ By default, deleting the environment variable sets the environment variable to **False**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/input-validation/appsec-cicd-186.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.