> 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/artifact-integrity-validation/appsec-cicd-125.md).

# Unpinned GitHub actions

## Rule Details

|                       |                               |
| --------------------- | ----------------------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_125             |
| Category              | Artifact Integrity Validation |
| Severity              | MEDIUM                        |

## Impact

Unpinned GitHub Actions are mutable, potentially allowing attackers with access to the action's repository to push a malicious version of the action, introducing poisoned code which can be executed in the pipeline in order to access stored secrets or to read or modify the source code.

## Recommended Solution - Buildtime

GitHub recommends pinning actions to a full length commit SHA, as this is currently the only method of using an action as an immutable release.

For more information refer to: <https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions>.


---

# 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/artifact-integrity-validation/appsec-cicd-125.md?ask=<question>&goal=<user_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.