> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/autofix-and-remediation/aikido-libraries-overview/patch-creation-sla.md).

# Patch Creation SLA

For every new CVE that is detected in an existing **Aikido Image**, or in an **Aikido Library**, the following SLA apply:

| Severity        | SLA                     |
| --------------- | ----------------------- |
| CISA KEV        | 48 hours                |
| Critical / High | 7 days                  |
| Medium / Low    | Commercially reasonable |

SLA timelines start once a CVE is published and a valid fix candidate is available in the upstream ecosystem.

### Scope: Bulk Rollout vs. one-off fixes

This SLA applies to **Aikido Libraries enrolled via Bulk Rollout** (AutoFix > Aikido Libraries > Bulk Rollout). One-off Aikido Libraries fixes taken from the Feed or from AutoFix > Dependencies, without enrolling the repository through Bulk Rollout, are not covered by this SLA.

### A note on pre-existing CVEs

**Aikido Libraries** - the SLA covers new CVEs that arise after you enroll your repository. Pre-existing CVEs will still be fixed, but they are not covered under the SLA commitment. This is because repositories can carry a large backlog of open CVEs at the time of enrollment, and working through that debt is handled separately.


---

# 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://help.aikido.dev/autofix-and-remediation/aikido-libraries-overview/patch-creation-sla.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.