{{ message }}
build: fix Dependabot alerts for log4j-core and opentelemetry-api#352
Merged
Conversation
The log4j-core force in the spotbugs configuration only covered subprojects, while the root project also has a spotbugs configuration that was resolving log4j-core 2.23.1 (CVE-2026-34477, CVE-2026-34478, CVE-2026-34480). Move the forced versions to allprojects so the root project is covered as well. Bump OpenTelemetry from 1.57.0 to 1.63.0 to address CVE-2026-45292 (unbounded memory allocation in W3C baggage propagation, fixed in 1.62.0). Signed-off-by: Matteo Merli <mmerli@apache.org>
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
1 participant
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.
Motivation
Fixes all 4 open Dependabot alerts:
log4j-core 2.23.1 (alerts Do not call getSession unecessarily #67, Make KeepAlives non-streaming #68, Fix flux instantiation on retry #69 — CVE-2026-34477, CVE-2026-34478, CVE-2026-34480): the version catalog already pins log4j 2.26.0, but the forced versions for the
spotbugstool configuration only coveredsubprojects. The root project also applies the SpotBugs plugin, so itsspotbugsconfiguration was still resolving log4j-core 2.23.1. Since Automatic Dependency Submission resolves every configuration, this single path kept the alerts open.opentelemetry-api 1.57.0 (alert min → start, max → end #72 — CVE-2026-45292, fixed in 1.62.0): Dependabot couldn't auto-bump it because the version is managed through the BOM platform.
Modifications
Move the spotbugs
resolutionStrategyforce block fromsubprojectstoallprojects(guarded byplugins.withId) so the root project's configuration is covered too. Verified that the rootspotbugsconfiguration now resolves log4j-core 2.26.0 and no configuration in any project resolves a version below 2.25.4.Bump OpenTelemetry 1.57.0 → 1.63.0 (latest stable), including the
opentelemetry-bom-alphaversion that is hardcoded in the catalog.Once merged, the next Automatic Dependency Submission run on
mainshould close all 4 alerts.