build(deps): bump x/crypto, x/net, x/oauth2, jwt/v5, logrus and protobuf - #9054
Merged
Conversation
golang.org/x/crypto v0.41.0 -> v0.55.0 (15 CVEs, 7 CRITICAL) golang.org/x/net v0.43.0 -> v0.58.0 (CVE-2026-25680) golang.org/x/oauth2 v0.13.0 -> v0.36.0 (CVE-2025-22868) 17 known CVEs in total. govulncheck confirms 8 of them are reachable from this code base: 6 in x/crypto, 1 in x/net and 1 in x/text -- x/text is pulled up by minimal version selection along with the rest of the golang.org/x set (x/sys, x/term, x/sync, x/mod, x/tools). After the bump govulncheck reports none of them. The reachable x/crypto findings are in the SSH stack and are reached through core/utils/io.go, where archives are copied with github.com/viant/afs -- that library registers an SSH/SCP backend, so ssh.Dial, ssh.ParsePrivateKey and the agent signer end up in the build graph. They are not reached through gitextractor: cloning is done by the git CLI, not by a Go SSH client. x/oauth2 is used directly by server/api/auth and helpers/oidchelper; its finding is a malformed token that allocates without bound during parsing. No source change was required -- none of the bumped packages changed an API surface this code base touches. Signed-off-by: DoDiODev <DoDiDev@proton.me>
… and protobuf github.com/golang-jwt/jwt/v5 v5.0.0-rc.1 -> v5.3.1 github.com/sirupsen/logrus v1.9.0 -> v1.10.0 google.golang.org/protobuf v1.31.0 -> v1.36.12 jwt/v5 was pinned to a release candidate published in March 2023. Besides being a pre-release in a security-sensitive position, v5.0.0-rc.1 is affected by CVE-2025-30204 (HIGH), which govulncheck reports as reachable from this code base. v5.3.1 is the current stable release. jwt/v5 is used by the GitHub App token flow (plugins/github/token, plugins/github/models/connection.go), the Teambition connection and the OIDC session helper (helpers/oidchelper/session.go). Moving from the RC to stable needed no source change; the signing, parsing and claims APIs used here are unchanged. logrus v1.9.0 (CVE-2025-65637, HIGH) and protobuf v1.31.0 (CVE-2024-24786) are bumped to current releases in the same pass. Verified with the unit tests of the affected packages, including server/api/auth (JWT session handling) and helpers/oidchelper. Signed-off-by: DoDiODev <DoDiDev@proton.me>
DoDiODev
added a commit
to DoDiODev/devlake
that referenced
this pull request
Aug 17, 2026
…e#9054 Re-checked before opening the upstream PR: x/net moved on to v0.58.0 and logrus to v1.10.0 since the wave was prepared on 2026-08-12. Signed-off-by: DoDiODev <DoDiDev@proton.me>
DoDiODev
added a commit
to DoDiODev/devlake
that referenced
this pull request
Aug 17, 2026
…e#9054 Re-checked before opening the upstream PR: x/net moved on to v0.58.0 and logrus to v1.10.0 since the wave was prepared on 2026-08-12. Signed-off-by: DoDiODev <DoDiDev@proton.me>
klesh
approved these changes
Aug 18, 2026
klesh
left a comment
klesh
left a comment
Contributor
There was a problem hiding this comment.
LGTM
Thanks for your contribution.
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
2 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.
Summary
Bumps six dependencies that carry known advisories. Touches
backend/go.modandbackend/go.sumonly — no source change was required.golang.org/x/cryptogolang.org/x/netgolang.org/x/oauth2github.com/golang-jwt/jwt/v5github.com/sirupsen/logrusgoogle.golang.org/protobufjwt/v5was pinned to a release candidate from March 2023 in asecurity-sensitive position (GitHub App tokens, OIDC sessions).
Reachability
govulncheck ./...inbackend/:upstream/main)go-git8,go-billy2,circl2,go-jose/v32 + stdlib)This PR removes the 6 reachable
x/cryptofindings, 1 inx/net, 1 inx/text(pulled up by MVS) and the
jwt/v5one. The reachablex/cryptoSSH findingscome from
core/utils/io.go, where archives are copied viagithub.com/viant/afs, which registers an SSH/SCP backend — not fromgitextractor, which clones with the git CLI.
Verification
go mod tidy— clean, no further changesgo build ./server/... ./core/... ./helpers/... ./impls/...— greenserver/…(incl.server/api/authJWT session handling),helpers/…(incl.oidchelper),core/…,plugins/github,plugins/teambition— greengovulncheck ./...before/after as aboveNotes
MVS also pulls up
x/sys,x/term,x/sync,x/mod,x/textandx/tools.CI
Verified on a fork run of the same workflows before opening this PR:
8/8 green
(lint, unit-test, e2e MySQL, migration-script-lint, config-ui, license header,
grafana dashboards, builder image).