Browser check · Official Docker images
Is your Docker base image still patched?
A tag like php:8.4.26-fpm-alpine3.24 stops getting fixes the day Docker builds the next patch: the image under it never changes again. A tag like node:22-alpine keeps getting them, but only when you pull or build again. Paste your Dockerfile, compose file or image names. For each official image the page says whether Docker still builds the tag, which patch it builds today, whether the release line or the base system is past end of life, and the tag to move to.
Check your images
The page reads FROM lines (with ARG defaults filled in), image: lines from compose, Kubernetes and GitHub Actions files, docker pull and docker run commands, and plain names such as python:3.12-slim, one per line. Other lines are ignored.
Check asks GitHub for Docker’s public build list of each official image you name (php, node, postgres…) and endoflife.date for the support dates of those products and, for the base your tag names or Docker builds it on, of alpine-linux, debian or ubuntu. Both see that the request came from this page. The page carries Docker’s list of official image names and asks about no other name, so your full tags, digests, the rest of your file and the names of your own images stay on this page. What is sent where
Result
How the page decides
- Still built or not comes from Docker’s own build lists for official images, the library files in docker-library/official-images. A tag listed there is rebuilt when its software or its base image is updated. A tag that has left the list is frozen: Docker Hub still serves it, but nothing changes it again.
- Pinned patch (
php:8.4.26): when Docker no longer builds it, the page gives the patch Docker builds today on the same release line and base, and the line tag (php:8.4-…) that follows each new patch. - Line tag (
node:22-alpine,redis:7): the page shows the patch it carries today. An image you built or pulled before keeps the old one until you build with--pullor pull again. - Tags with no version (
latest,alpine,fpm) follow whatever Docker makes newest and can move to a new release line or base without notice. The page names the line they carry today. - End of life for the software line and for the base (Alpine, Debian, Ubuntu) comes from endoflife.date. Past that date its makers ship no fixes, even if Docker still rebuilds the tag.
- Digests (
@sha256:…): what you run never changes. The page judges the tag next to the digest.
What it doesn’t check
- Package vulnerabilities (CVEs) inside the image. The page checks release versions and whether Docker still rebuilds a tag, which is what decides whether fixes can reach you. A scanner such as
docker scout cves, Trivy or Grype lists the packages in the image you actually have. - Images that are not official Docker images (
bitnami/…,ghcr.io/…, your own). Their publishers decide when to rebuild; the page names them and sends nothing about them. - Windows images, and images on registries that mirror Docker Hub under another name.
Doing it without this page
Your coding agent can do the same reads, or you can: open the image’s file under library/ in docker-library/official-images and search for your tag, then look up the release line on endoflife.date. docker buildx imagetools inspect IMAGE:TAG shows the digest Docker serves today, so you can compare it with the one you run. This page does those reads for every image in your file at once.
Security releases we have written up
When your tag is older than one of these releases, the result links the guide. Each guide lists the fixed versions, the Docker tags that carry them and how to check the image you run.