Repository navigation
Fix CVE-2026-111497 and CVE-2026-114406 - #5
Merged
Merged
Conversation
|
I was just about to push something like 0cecd86 😅 |
It made it further but it's still failing. |
Member
Author
|
Postgres having a GIS extension for geographic data is new to me 🙃. Bumping it is a CI fix only -- we don't actually make use of it in DE 5. |
antoinerg
approved these changes
Nov 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Manual image build and push needed after merge. No CI pushes this image to quay. The inherited
publish-ghcr-container.yamlonly targets ghcr.io and failed on its one run. The 5.8 image isquay.io/plotly/spilo:17.10-4.0-p3, a single-arch amd64 image built by hand. The new image gets the next patch tag,17.10-4.0-p4. Do not overwrite17.10-4.0-p3, because running installs pull it.Steps, on an amd64 host (the build compiles wal-g and is slow under emulation):
5.8-releaseafter this PR merges:quay.io/plotly/spilo:libbrotli11.0.9-2ubuntu0.1andca-certificates20260816ubuntu0.22.04.1.5.8-release, replace17.10-4.0-p3with17.10-4.0-p4in every file that names it:application.yaml,imageswap/imageswap-map.yaml,postgres-cluster/postgresql.yaml,postgres-operator.yaml,postgres-operator/values.yamland the operator configuration CRD default.Upgrades
libbrotli1andbrotlifor CVE-2026-111497 (DASH-2660) in the DE 5.8 spilo image,quay.io/plotly/spilo:17.10-4.0-p3.Change
A step after
base.shupgrades both packages and fails the build unlesslibbrotli1is at least1.0.9-2ubuntu0.1.base.shinstalls packages but does not upgrade ones that are already installed. The step sits before theCOMPRESSstage, so it covers both build modes.POSTGIS_VERSIONmoves from 3.6 to 3.7. PGDG now installs PostGIS 3.7.0 by default, sobase.shfailed on the missingcontrib/postgis-3.6directory. DE does not use PostGIS.wal-g statically links its own brotli, which
libbrotli1does not cover.WALG_REFmoves to wal-g67cb69a4, which bundles brotli v1.2.1 with the CVE-2026-111497 fix. That commit needs Go 1.27.3, which also fixes CVE-2026-111943. wal-g is now built withUSE_LZO=1, so it can restore LZO backups again;liblzo2-devwas already installed for this. The tests now use SeaweedFS instead of MinIO, as upstream did in zalando#1218, because the MinIO image can no longer be pulled.base.shnow keeps the timescaledb libraries that every PG major shares with the oldest one, from zalando#1173. The current timescaledb packages pruned 2.19 from PG 15, so the in-place 14 to 15 upgrade test failed on a missing library. DE does not use timescaledb or in-place major upgrades.Testing
On
ubuntu:22.04(arm64), I installed the vulnerable1.0.9-2build6packages and then ran the step. Both packages ended at1.0.9-2ubuntu0.1.After merge
See the build and push steps at the top.
CVE-2026-114406, eMudhra roots (DASH-2715)
The leaked eMudhra intermediates chain to emSign ECC Root CA - G3 and to Comodo AAA Certificate Services, which cross-signed them. emSign Root CA - C1 and emSign ECC Root CA - C3 stay trusted, as in the distribution's package and in DE6 (dash-enterprise#883).
ca-certificatesto Ubuntu's fixed20260816ubuntu0.22.04.1, which drops both.patroni_wale.shupgrades certifi to 2026.10.23 or later. Patroni's Kubernetes client uses certifi. 2026.10.19 is the first release without G3 and Comodo AAA, and 2026.10.23 also drops C1 and C3.Tested on
ubuntu:22.04: the bundle contains neither G3 nor Comodo AAA.