All blog posts
Updates 2 min read

Commonveil Fixes a zlib Finding in Docker Images

A Docker build change required a fixed zlib version and applied Alpine security updates to both the site and updater images.

By Comutability Published Update from

Project update: 13 November 2026. GitHub pull request #5: merged into GitHub source, not necessarily deployed. Commonveil has not been independently security audited.

A Docker build change required a fixed zlib version and applied Alpine security updates to both the site and updater images.

Why this matters

A vulnerability in an upstream image should not be waved away solely because the affected function appears unreachable. The project documented its exposure assessment and tightened build requirements so an old image cannot silently reintroduce the version in question.

Detailed change record

The public engineering notes below describe what was implemented or proposed and the evidence recorded with the change. Historical instructions in the notes describe the pull request at the time it was raised.

Fixes Snyk's finding CVE-2026-4738 (zlib in Alpine 3.24, below 1.4-r0, rated low).

Cause: both Docker images start from node:26-alpine. That image was built before Alpine published zlib 1.4-r0 on 6 November.

Fix:

  • The final stage of both images (site and updater) now runs apk upgrade --no-cache && apk add --no-cache "zlib>=1.4-r0". This picks up all of Alpine's security updates when the image is built.
  • The version constraint makes the build fail if the fixed zlib isn't available. A rebuild from an older base can't quietly ship the old zlib again.
  • CI prints the installed zlib in each image.
  • docs/SECURITY_REVIEW.md records the finding.

Exposure: upstream, this flaw is in zlib's infback9 contrib code as bundled in GDAL. Commonveil never calls that code, so it wasn't reachable. It's fixed anyway, so the image is clean.

Not verified locally: Docker Hub is blocked from the environment I work in, so the images couldn't be built there. The images job in CI builds and starts both images, and that is the check for this change.

Decisions and principles behind the work

Comutability is building towards privacy, user control and genuinely self-hostable software. That does not mean every proposal is already deployed. Cryptography and security improvements need qualified human review and meaningful tests before any strong safety promises are made.

What comes next

Use CI and rebuilt images to verify the fix, while continuing to check whether upstream findings are relevant to the actual application.

Check the sources

Sources and further reading

Explore the evidence and original project records behind this article.