# Chainguard products changelog

URL: https://deploy-preview-3798--ornate-narwhal-088216.netlify.app/chainguard/changelog.md
Last Modified: August 17, 2026
Tags: Chainguard Containers, Changelog

Weekly changelog of Chainguard product updates — product announcements, breaking changes, container images reaching end-of-life or leaving the catalog, and images newly added to it.

This page logs Chainguard product updates week by week, newest first: product announcements, breaking changes, container images that reached end-of-life or are no longer available, and images newly added to the catalog. Each event is listed once, in the week it first appeared.
Week of 2026-08-17 Product Announcements Clearer npm errors for blocked packages Launched August 13, 2026.
When Chainguard Libraries withholds an npm package or version — because of detected malware or greyware, a pending malware scan, or a policy block such as a cooldown — npm now returns a 403 naming the specific reason, for example MALWARE_DETECTED, instead of the unexplained 404 it returned before. The other supported package managers (pnpm, yarn, uv, poetry, Maven, and Gradle) still report a blocked version as a generic not-found error, and a 409 when an entire package is blocked for malware.
For more information, refer to Error messages.
Guardener GitHub App (beta) Launched August 12, 2026.
Chainguard Guardener, the automated migration tool, now covers GitHub Actions as well as container images. The GitHub App inventories the Actions in use across your organization’s repositories, maps them to hardened Chainguard equivalents, and opens pull requests to swap them in, pinned to a specific SHA rather than a mutable tag. It runs in two modes: an upfront pass that surfaces existing Actions usage and opens migration pull requests, and ongoing standardization that watches workflow files and suggests Chainguard equivalents as new upstream Actions appear.
For more information, refer to Getting started with Chainguard Guardener.
Breaking Changes Chainguard Libraries build pinning Effective August 24, 2026.
Chainguard Repository can serve two copies of the same package version: the upstream copy mirrored from the public registry, and Chainguard’s copy rebuilt from source. The two have different checksums, and each request resolves independently, so when Chainguard publishes a rebuild of a version your organization already pulled, the next resolution moves you to the rebuild and its checksum no longer matches your lockfile — surfacing client-side as errors such as EINTEGRITY in npm. As of August 24, 2026, build pinning records which copy your organization received the first time it downloads a package version and keeps resolving that version to the same copy until you choose to move forward. Malware and policy blocks apply independently: a version that is later blocked stops being served rather than being replaced with a different copy.
Affected: organizations using Chainguard Libraries with upstream fallback, across JavaScript, Python, and Java. Organizations without upstream fallback see no change. Action: none required. To keep the current behavior, run chainctl libraries cache opt-out. Both opt-out and chainctl libraries cache opt-in accept --ecosystem, and pinning state is tracked per organization and ecosystem. To see which copy each held version came from, run chainctl libraries cache list. For more information, refer to chainctl libraries cache.
EOL Chainguard offers a grace period for eligible end-of-life images: up to six months of continued rebuilds and security updates while you complete your upgrade.
Images that are no longer available The following container images reached the end of their grace period and are no longer available:
Image End-of-life Grace period ended prometheus:3.9 2026-02-17 2026-08-17 Images that have reached end-of-life The following container images reached end-of-life and entered their grace period:
Image End-of-life Grace period ends mattermost:10.11 2026-08-15 2027-02-15 New Images Chainguard built 17 new container images this week, including both standard and FIPS variants.
ImageTierAdded azuriteapplication2026-08-10 k0s-cni-nodeapplication +fips2026-08-10 peerdb-uiapplication +fips2026-08-10 sccapplication +fips2026-08-10 zitadel-loginapplication2026-08-11 aws-lambda-nodejsapplication +fips2026-08-12 localstackapplication2026-08-12 kserve-router-fipsfips2026-08-13 jdk-openssl-fipsfips2026-08-14 jre-openssl-fipsfips2026-08-14 kube-routerapplication +fips2026-08-14 commercial-nginx-ingress-pluscommercial2026-08-17 Week of 2026-08-10 Product Announcements Chainguard Libraries available through AWS Security Hub Extended Launched August 4, 2026.
AWS added a Supply Chain category to Security Hub Extended and named Chainguard one of its inaugural partners. You can now subscribe to Chainguard Libraries from the Security Hub console and pay through your existing AWS account. Libraries findings arrive normalized to the Open Cybersecurity Schema Framework (OCSF), so they appear alongside your AWS and other partner findings, and AWS Enterprise Support customers receive Level 1 support from AWS.
For more information about the catalog, refer to the Chainguard Libraries overview.
Malware avoidance in the Console (beta) Launched August 4, 2026.
The Console now shows which malicious and suspicious packages Chainguard Libraries blocked before they reached your environment. A weekly chart tracks the malware and greyware stopped across the Python and JavaScript ecosystems, and a search tool reports why any given package was flagged unsafe. Find it under the Malware tab in the Libraries section of the Console sidebar; it is enabled by default for every organization entitled to Libraries.
For more information, refer to View malware information.
PKCE support for custom identity providers Launched August 3, 2026.
Chainguard now supports Proof Key for Code Exchange (PKCE) on the OAuth token exchange with custom OIDC identity providers, in line with OAuth 2.1. Administrators can enable it with chainctl or the Chainguard API, either alongside an existing client secret or as a secret-free public client.
For more information, including setup steps, refer to Enable PKCE for OAuth Token Exchange.
EOL Chainguard offers a grace period for eligible end-of-life images: up to six months of continued rebuilds and security updates while you complete your upgrade.
Images that have reached end-of-life The following container images reached end-of-life and entered their grace period:
Image End-of-life Grace period ends net-kourier:1.21 2026-08-04 2027-02-04 tekton-pipelines:1.3 2026-08-04 2027-02-04 ruby3.2-rails:7.2 2026-08-09 2027-02-09 ruby3.3-rails:7.2 2026-08-09 2027-02-09 ruby3.4-rails:7.2 2026-08-09 2027-02-09 ruby4.0-rails:7.2 2026-08-09 2027-02-09 New Images Chainguard built 23 new container images this week, including both standard and FIPS variants.
ImageTierAdded prometheus-stackdriver-exporterapplication +fips2026-08-03 crossplane-azure-keyvaultapplication2026-08-04 crossplane-azure-kustoapplication2026-08-04 influxdb-fipsfips2026-08-04 moodle-iamguardedapplication2026-08-04 pypiserver-fipsfips2026-08-04 kubevirt-cdi-clonerapplication +fips2026-08-05 yopassapplication2026-08-05 acm-controllerapplication +fips2026-08-06 gremlin-serverapplication2026-08-06 rollouts-plugin-trafficrouter-gatewayapiapplication +fips2026-08-06 claudeapplication2026-08-07 codexapplication2026-08-07 cruise-controlapplication +fips2026-08-07 dotstatsuite-supercoreapplication2026-08-07 opencodeapplication2026-08-08 zalando-pgbouncerapplication +fips2026-08-10 Week of 2026-08-03 Breaking Changes ingress-nginx-controller entrypoint, command, and default user changes Effective July 15, 2026.
Chainguard aligned the entrypoint and command behavior of all supported ingress-nginx-controller images with the upstream image, correcting a startup configuration defect present since the image was first published in 2024. Non-iamguarded variants also changed their default runtime user from root (UID 0) to www-data (UID 101).
Affected: all supported ingress-nginx-controller images, including FIPS and -iamguarded variants. Action: review any configuration that overrides command, args, entrypoint, or runAsUser, or that depends on admission policies or file ownership assumptions. Deployments using the upstream Helm chart defaults need no changes. EOL Chainguard offers a grace period for eligible end-of-life images: up to six months of continued rebuilds and security updates while you complete your upgrade.
Images that are no longer available The following container images reached the end of their grace period and are no longer available:
Image End-of-life Grace period ended cilium:1.16 2026-02-03 2026-08-03 neo4j:2025.12 2026-02-03 2026-08-03 Images that have reached end-of-life The following container images reached end-of-life and entered their grace period:
Image End-of-life Grace period ends eks-distro:1.33 2026-07-29 2027-07-29 mongo:8.2 2026-07-31 2027-01-31 prometheus:3.5 2026-07-31 2027-01-31 cockroach:26.1 2026-08-02 2027-02-02 cockroach-openssl:26.1 2026-08-02 2027-02-02 New Images Chainguard built 18 new container images this week, including both standard and FIPS variants.
ImageTierAdded atlasapplication +fips2026-07-29 azure-metrics-exporterapplication +fips2026-07-29 crossplane-azure-solutionsapplication2026-07-29 crossplane-azure-streamanalyticsapplication2026-07-29 crossplane-azure-webapplication2026-07-29 dns-controller-managerapplication +fips2026-07-29 instrumentisto-harakaapplication +fips2026-07-29 openstack-kolla-toolboxapplication +fips2026-07-29 sftpgoapplication2026-07-29 flink-kubernetes-operator-fipsfips2026-07-30 traccarapplication +fips2026-07-30 metacontroller-fipsfips2026-07-31 Week of 2026-07-28 Product Announcements SUSE NeuVector now natively supports Chainguard Containers Launched July 24, 2026.
SUSE’s NeuVector vulnerability scanner now natively supports Chainguard Containers and ingests Chainguard’s OSV advisory feed, which includes recent data-quality improvements. Scans of Chainguard images suppress false positives and report more accurate results.
Group-based role mapping is now generally available Launched July 22, 2026.
Administrators can map identity provider groups — Okta or Microsoft Entra ID, for example — directly to Chainguard roles, instead of assigning roles one user at a time. Anyone who authenticates with a mapped group in their token receives that role for the session.
For more information, including setup steps, refer to Grant Chainguard roles from identity provider groups.
EOL Chainguard offers a grace period for eligible end-of-life images: up to six months of continued rebuilds and security updates while you complete your upgrade.
Images that are no longer available The following container images reached the end of their grace period and are no longer available:
Image End-of-life Grace period ended knative-eventing:1.19 2026-01-28 2026-07-28 knative-serving:1.19 2026-01-28 2026-07-28 net-kourier:1.19 2026-01-28 2026-07-28 Images that have reached end-of-life The following container images reached end-of-life and entered their grace period:
Image End-of-life Grace period ends dnsdist:1.9 2026-07-21 2027-01-21 longhorn-backing-image-manager:1.8 2026-07-22 2027-01-22 longhorn-instance-manager:1.8 2026-07-22 2027-01-22 envoy:1.35 2026-07-23 2027-01-23 New Images Chainguard built 15 new container images this week, including both standard and FIPS variants.
ImageTierAdded coderapplication +fips2026-07-22 flink-kubernetes-operatorapplication2026-07-22 pgheroapplication +fips2026-07-22 kargoapplication2026-07-23 nuclio-controllerapplication +fips2026-07-23 phpmyadminapplication +fips2026-07-23 apache-exporter-iamguardedapplication2026-07-24 glabapplication +fips2026-07-27 metabaseapplication2026-07-27 crossplane-azure-relayapplication2026-07-28