Repository navigation
[cloud-provider-yandex] Fix CVE - #32
Merged
Merged
Conversation
Signed-off-by: Sergey Petrov <sergey.petrov@flant.com>
ptrvsrg
force-pushed
the
fix/cve-yandex-csi
branch
from
July 15, 2026 10:58
4ad8f11 to
b198008
Compare
ptrvsrg
marked this pull request as ready for review
July 16, 2026 07:46
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.
Description
Updated Go dependencies for the Yandex CSI driver to remediate CVEs, including
google.golang.org/grpc.Also updated the build and CI toolchain:
golang:1.25.12-alpine3.24with digest pinning;alpine:3.24with digest pinning;1.25.12;golangci-linttov2.8.0.This affects the Yandex CSI driver image. During delivery in Deckhouse, CSI controller/node pods using the updated image are expected to roll out; no storage migration is intended.
Why do we need it, and what problem does it solve?
The Yandex CSI driver used vulnerable Go dependencies reported by CVE scanning.
The old Dockerfile and CI Go versions were also incompatible with the updated dependency stack. The change updates the dependency stack and aligns the build/CI toolchain with Go
1.25.12and Alpine3.24.Why do we need it in the patch release (if we do)?
Not necessarily
Checklist
Changelog entries