Fix dependency vulnerabilities from image scans and Dependabot - #6811
Merged
Conversation
Fixes CVE-2026-39822 and CVE-2026-42505 flagged by ECR Inspector on the compiler-server image. The remaining goroot x/crypto and x/net findings are CVEs in packages the Go stdlib does not vendor (ssh among others); they clear with Go 1.27, currently at rc2. Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
aws-smithy-json 0.62.7 (CVE-2026-18140), reqsign family (moves one quick-xml copy to 0.41.0, RUSTSEC-2026-0195), tokio-postgres 0.7.18 and postgres-protocol 0.6.12 (RUSTSEC-2026-0178/0179/0180, crates.io copies; the supabase etl git fork still pins the old versions), crossbeam-epoch 0.9.20 (RUSTSEC-2026-0204). aws-smithy-types stays at 1.5.0 and aws-smithy-runtime-api-macros at 1.0.0: newer versions require rustc 1.94.1, the workspace pins 1.93.1. Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
yarn.lock: brace-expansion 1.1.18, fast-uri 3.1.5, postcss 8.5.23, svgo 3.3.4, webpack-dev-server 5.2.6, dompurify 3.4.12 (Dependabot HIGH/MEDIUM/LOW). uv.lock: soupsieve 2.9.1 (CVE-2026-49476, CVE-2026-49477). Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
All workspace copies move to at least 2.69.1, the first fixed version. Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
Fixes GHSA-6v7p-g79w-8964. Also syncs the stale locked dbt-feldera version to pyproject.toml. Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
mihaibudiu
approved these changes
Aug 5, 2026
gz
enabled auto-merge
August 5, 2026 17:44
mythical-fred
approved these changes
Aug 5, 2026
mythical-fred
left a comment
There was a problem hiding this comment.
Straightforward security/dep bumps. Go 1.26.5, aws-smithy-json 0.62.7, reqsign family, tokio-postgres, crossbeam-epoch, and the yarn/uv/bun lockfile churn (dompurify, brace-expansion, postcss, svgo, webpack-dev-server, @sveltejs/kit, soupsieve, msgpack). Commit history is clean (one commit per ecosystem) and the PR body enumerates every advisory. cargo check was run and the reqsign-core 3.2 / reqsign-google 3.0.4 API break was fixed in-tree — good catch, that's the kind of thing that would silently break a cargo update sweep.
No Cargo.toml public-API changes beyond the reqsign version pins; SvelteKit 2.60→2.69 is a minor-only jump. LGTM.
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
3 participants
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.
Fixes the dependency vulnerabilities from the ECR Inspector scan of the compiler-server image and the open Dependabot alerts that are fixable today. Lockfile-only where possible; no API migrations.
Fixed
Validation
cargo check -p pipeline-manager -p dbsp_adapterspasses (caught and fixed a real reqsign-core 3.2 / reqsign-google 3.0.1 API mismatch).