- Task
- Version · 6.0.2
- Create
Scan Liquibase Secure server images for vulnerabilities
Last updated: November 17, 2026
A Liquibase Secure server deployment runs Liquibase images and third-party images from Docker Hub. You can scan each of them with your own vulnerability scanner, such as Trivy or Grype, the same way you scan any other container image.
Before you begin
You must have installed Liquibase Secure server 6.0.2, as in Install Liquibase Secure server or Install Liquibase Secure server in a restricted or air-gapped network.
You must have Trivy or Grype installed on the host that runs the server.
Procedure
List the images your deployment runs
The status command lists each running service and, in its Image column, the image the service runs. Be sure to replace your_deployment_directory with the directory you installed into. For example, /opt/liquibase-platform
./liquibase-platform status --dir your_deployment_directoryA 6.0.2 deployment that you installed with your license file runs these images:
Image | What it runs |
| The API |
| The web console |
| The database migrations. |
| The proxy that serves the console and the API over HTTPS |
| The server's database and its secrets database. With an external PostgreSQL database, only the secrets database runs. |
| Redis, which carries the console's live updates |
If you installed from your own registry, the Liquibase images start with your registry path instead of oci.liquibase.com. The third-party images do too if you copied them with --include-third-party. The Image column always shows the names your deployment uses.
Liquibase also publishes a liquibase-platform-llt image with each release, and pull copies it to your registry. A deployment does not run it.
Scan the images
You only need one scanner, Trivy or Grype. Run it on the host that runs the server. Both scanners read an image from the local Docker engine when it is there, so they scan the images your deployment pulled, and you do not log in to oci.liquibase.com. On another host, scan your copy in your own registry instead.
If your deployment's images come from your own registry, replace oci.liquibase.com in these commands with your registry path from step 1.
To scan the three Liquibase images with Trivy, run:
To scan them with Grype instead, run:
Scan the third-party images the same way, with the names from step 1. For example, to scan the PostgreSQL image with Trivy, run:
trivy image postgres:17.11-alpineEach scanner prints a table of the packages in the image that have known vulnerabilities, with the installed version, the fixed version when one exists, and the severity.
Review the findings
Liquibase Secure server 6.0.2 does not include VEX (Vulnerability Exploitability eXchange) documents for its images. Your scanner reports every finding in the Liquibase images, including any that Liquibase has assessed as not exploitable in Liquibase Secure server.
The VEX files for Liquibase Secure cover the liquibase command-line distribution, not the server images. The public Liquibase VEX repository also holds statements for the server image names, but those statements name the ghcr.io/liquibase and registry.liquibase.com registries, which 6.0.2 does not install from. Trivy and Grype match a VEX statement to an image by its registry, so trivy image --vex repo and grype --vex do not suppress any finding in an image from oci.liquibase.com or from your own registry.
To find out whether a finding in a Liquibase image affects Liquibase Secure server, contact Liquibase support. Include the image name, the CVE or advisory ID, and the package the scanner names.
The nginx, PostgreSQL, and Redis images are the official Docker Hub images. Liquibase does not build them, so their findings come from those images as Docker Hub publishes them.