Repository navigation
Bump vespa-feed-client to 8.763.13 + grpc 1.83.2 (3 HIGH CVEs) - #2010
Merged
Merged
Conversation
…6-89407, CVE-2026-89425) vespa-feed-client 8.738.17 pulled jackson-core 2.22.1; 8.763.13 pulls 2.22.3 and Bouncy Castle 1.86, so the Bouncy Castle pins are no longer needed. Also bumps guava 33.7.2-jre (client-java) and logback-classic 1.6.5 (book-search). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch was successfully deployed
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.
Summary
Bumps
vespa-feed-clientfrom 8.738.17 to 8.763.13 in the two examples that pin it. The old version pulledjackson-core2.22.1, which has two HIGH CVEs. Also bumpsgrpcin the Go cloud-functions example.Changed Files
examples/clients/client-java/app/build.gradle.ktsvespa-feed-client:8.738.17→8.763.13(bringsjackson-core2.22.3)constraintsblock. 8.763.13 resolvesbcprov/bcpkix/bcutil1.86 without it, so the pin's own "until the platform ships 1.86" condition is met.examples/clients/client-java/gradle/libs.versions.tomlguava:33.7.1-jre→33.7.2-jreexamples/book-search/pom.xmlvespa_version(vespa-feed-client):8.738.17→8.763.13. Mend only flagged client-java, but this pom pinned the same version.logback-classic:1.6.4→1.6.5dependencyManagementpins, for the same reason as above.examples/google-cloud/cloud-functions/go/go.modgoogle.golang.org/grpc:1.83.1→1.83.2(CVE-2026-84445, Dependabot alert Add System Test section #425)CVEs Addressed
Verified against the GitHub Advisory Database:
These are still live on VESPANG-3395. None of them has a fixed release yet:
Supersedes
Implementation Notes
junit-jupiterin book-search stays on 5.14.4. 6.x is a major bump, and the test scope can't be resolved outside Vespa:ai.vespa:vespa-testcontainers:1.0.0isn't on Maven Central (see the book-search README). So a 6.x bump can't be checked here.slf4j-simplestays on 2.0.20. The only newer version is2.1.0-alpha1.go get -usweep raises thegodirective to 1.26, and the README deploys with--runtime=go119, so it would also mean changing the documented runtime. Note that the example has nogo.sumon master, sogo buildfails there with or without this change.Verification
All builds ran in throwaway containers:
gradle:jdk21):gradle :app:dependencies --configuration runtimeClasspathshowsjackson-core:2.22.3and Bouncy Castle1.86, andgradle buildpasses.maven:3-eclipse-temurin-17):mvn dependency:treeshowsjackson-core:2.22.3and Bouncy Castle1.86, andmvn compilepasses. This used a copy without the unpublishedvespa-testcontainerstest dependency, so the tests were not compiled or run.mvn installCI build.PR authored by the auto security-workflow skill.
🤖 Generated with Claude Code