> 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-images.md).

# Aikido Images

Updating to the latest version of a base image can be difficult because it may require changes to your application. When updating to a newer base image is not a viable option, you can stay secure by using **Aikido Images**.

Aikido Images is a registry of zero-CVE base images: drop-in replacements that carry patched versions of libraries with reported **CRITICAL** or **HIGH** severity security issues.

{% hint style="info" %}
Aikido Images cover OS-level CVEs under a defined [patch creation SLA](/autofix-and-remediation/aikido-libraries-overview/patch-creation-sla.md). Application-level package vulnerabilities (Python, npm, Java, Go, etc.) are also fixed, but on a best-effort basis with no guaranteed SLA. For guaranteed application-level coverage, see [Aikido Libraries](/autofix-and-remediation/aikido-libraries-overview.md).
{% endhint %}

For example, [CVE-2025-4373](https://security-tracker.debian.org/tracker/CVE-2025-4373) is fixed by Debian in Trixie and Sid but not in Bookworm. The Aikido Images variant of `debian:bookworm` contains a patched version of `glib2.0` that fixes this vulnerability. Using this image avoids breaking changes while maintaining a good security posture.

## Aikido Images availability <a href="#aikido-images-availability" id="aikido-images-availability"></a>

You can check the available images on <https://images.aikido.dev/> or in the Aikido UI under [AutoFix > Aikido Images](https://app.aikido.dev/issues/aikido-images).

A subset of the Aikido Images is available on [the public ECR gallery](https://gallery.ecr.aws/). These images are identical to the images in the `docker.aikido.io` registry and are updated on the same cadence. The public images can be pull from the public ECR and `docker.aikido.io`.

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-ec5aa7300789db2c4e84451a3f5e6f2c07a6c4bd%2FAutoFix_Container_overview_-_Roland_Demo_Org_-_Aikido_Security_%E2%80%94_Aikido.png?alt=media" alt=""><figcaption></figcaption></figure>

## See also

{% content-ref url="/pages/NgYUbx12E86BLPyg3v58" %}
[AutoFix for Containers: Aikido Images](/autofix-and-remediation/aikido-images/autofix-for-containers-using-aikido-images.md)
{% endcontent-ref %}


---

# 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-images.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.