Clearing CVEs by Cutting the Quine Container Images to 16 OS Packages
Lately it seems like a new CVE comes out every day, and we race to find a patch. A container image built on a full Ubuntu userland makes that worse, because it carries operating system packages our products never use and a vulnerability scan reports on every one of them. Our images now hold only what the products need to run, plus a few tools for working with a running container. A package that is not in the image has no CVEs to find and nothing to patch.
Starting with Quine 2.2.2, Quine Enterprise 2.2.2 and Novelty 1.2.1, the images are built differently, and a Trivy scan on November 18, 2026 reported zero OS-level findings on each of them. This post covers how the images are put together, our move to a Java distribution that had a fix out the day a JVM vulnerability was disclosed, and what changes for you when you run them.
An image with 16 Ubuntu packages
We chose each package in the image for one of three reasons. The first is that the product needs it to run: glibc for the Java runtime and the native libraries in our JARs, libstdc++ and libgcc for RocksDB, zlib for the Java runtime, and locale data so the JVM handles UTF-8. The second is that you need it to work with a running container, which is why bash and tools such as ls, cat, grep and find are there for docker exec, scripts and probes. The third is that the image has to stay clean without constant work. A tool went in only when its package and the libraries it needs had no open CVE in a Trivy scan, and a short list leaves fewer packages to watch and rebuild for when the next CVE is disclosed.
The earlier images started from a full Ubuntu userland with the Java runtime on top, followed by apt-get upgrade. The images are now built with Canonical's chisel tool, which cuts "slices" (subsets of files) out of Ubuntu 24.04 packages. The final image is FROM scratch, so it holds those slices, the Java runtime and the application, and nothing else. The Java runtime is copied in from the JDK vendor's image.
The result is 16 Ubuntu packages, slices of base-files, base-passwd, libc6, libc-bin (locale data), libstdc++6, libgcc-s1, zlib1g, bash, coreutils, grep, findutils, and the libraries those depend on. There is no curl, no apt, no package manager, and no ps, tar, cp, mv or sed.
Making Trivy see all 16 packages
Chisel records what it installed in its own manifest, /var/lib/chisel/manifest.wall, and Trivy does not read that file. Left alone, a scan of a chiseled image reports 0 OS packages. That looks clean, and it is misleading, because the packages are still there and their CVEs are still real.
So the build writes one dpkg status record per package into /var/lib/dpkg/status.d/, the same layout distroless images use, and fails the build if the number of records does not match the number of packages in the chisel manifest. Trivy lists the 16 OS packages and reports 0 findings on each of the three images. The zero is a result of scanning the packages, not of the scanner being unable to see them.
The Quine image also carries an SBOM attestation, so you can check the package list yourself without running a scanner, for example with docker buildx imagetools inspect thatdot/quine:2.2.2 --format '{{ json .SBOM }}'.
Other scanners can disagree. Trivy leaves out CVEs that Ubuntu has marked as ones it won't fix, and a scanner that includes them, such as Grype, lists findings on the same images.
A fixed JVM the day after disclosure
CVE-2026-114938, nicknamed "Java4Shell", was disclosed on November 17, 2026. It is memory corruption in the OpenJDK Base64 decoder intrinsic, and it affects OpenJDK 17.0.6 and later on x86-64 CPUs with AVX-512 VBMI. It is fixed upstream in OpenJDK 21.0.13.1+2.
A JVM flag, -XX:-UseBASE64Intrinsics, turns the faulty code path off. That is a reasonable stopgap, but a fixed runtime is the real answer. Amazon Corretto 21.0.13.1.2 shipped with the fix on the day of disclosure, and as of November 18, Eclipse Temurin had no fixed 21 release yet. How fast a vendor ships a fix matters when new CVEs keep coming, so we moved the images from Temurin to Corretto. The images with the fixed runtime shipped on November 18, the day after disclosure.
If you run an earlier release, upgrade to Quine 2.2.2, Quine Enterprise 2.2.2 or Novelty 1.2.1 to get the fixed runtime. Until you can, set the flag on x86-64 hosts with AVX-512 VBMI, for example with the environment variable JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics.
JAVA_HOME stays /opt/java/openjdk, so nothing that points at it needs to change. One difference is worth knowing about. The Corretto image carries the Amazon Linux root certificates, a somewhat different set from the Temurin image's. Most roots are in both, including the roots for AWS, Let's Encrypt, Google, Microsoft and DigiCert, but a few exist in only one of the two sets. Some of that difference is deliberate, because Corretto no longer trusts the compromised eMudhra roots (CVE-2026-91403, CVE-2026-114820). If you connect to an endpoint signed by an unusual root, check it against the Corretto set.
What changes when you run it
The HEALTHCHECK has to work without curl. The Docker HEALTHCHECK uses bash's /dev/tcp to send an HTTP request to the liveness endpoint and checks that the status line carries a 2xx code. The port comes from the QUINE_HEALTHCHECK_PORT environment variable and defaults to 8080, so set it if your web server listens elsewhere.
On Kubernetes, our Helm charts use httpGet probes, which need nothing inside the container. When mTLS moves the health endpoints to 127.0.0.1, where the kubelet can't reach them, the charts switch to an exec probe that sends the same request through /dev/tcp. If your own manifests run curl in a probe, switch them to httpGet.
A few habits need adjusting:
- Extending the image with
apt-getno longer works. Use a multi-stage build and copy the files you need into your own image. - Custom CA certificates go into the Java trust store with
keytool -importcert -cacerts, from an init container or in a derived image. - Some shell tools are gone, and the next section shows what to use in their place.
Working without cp, tar and ps
The image keeps bash and the everyday tools, ls, cat, grep, find and their like. A few familiar ones are missing. ps and top come from procps, which needs libsystemd, and tar is a package of its own. Both bring open CVEs. cp has no CVE of its own. Chisel offers it only in a coreutils slice that also holds wc, tee and sort, and that slice needs OpenSSL, which the image leaves out, so those three are missing too.
mv and sed were the only tools that needed libacl1, which has two CVEs rated High under CVSS 4.0. Ubuntu marked them won't fix for 24.04, but we wanted them out of the image anyway, so mv and sed went with libacl1.
Bash stands in for the common cases:
| Task | Command |
|---|---|
| Copy a file | cat <source> > <destination> |
| Move a file | cat <source> > <destination> && rm <source> |
| List processes | grep -H Name /proc/[0-9]*/status |
| Test a TCP port | (exec 3<>/dev/tcp/127.0.0.1/8080) && echo open |
kubectl cp runs tar inside the container, so it fails. Copy a file out, a heap dump for example, with kubectl exec <pod> -- cat <file> > <local file>, and copy one in with kubectl exec -i <pod> -- bash -c 'cat > <file>' < <local file>. docker cp still works. When you want a full toolbox on Kubernetes, attach a debug container with kubectl debug -it <pod> --target=<container> --image=busybox.
Getting it
The chiseled images ship in Quine 2.2.2, Quine Enterprise 2.2.2 and Novelty 1.2.1. If you build on top of our images, look at the list of habits above and adding packages to the image in our docs before you upgrade, especially anything that relies on apt-get, curl, tar, mv, sed or kubectl cp inside the container.