fix(deps): upgrade micronaut-micrometer to 5.13.3 (COMP-2258) - #1124
Closed
cristianrcv wants to merge 1 commit into
Closed
fix(deps): upgrade micronaut-micrometer to 5.13.3 (COMP-2258)#1124cristianrcv wants to merge 1 commit into
cristianrcv wants to merge 1 commit into
Conversation
micrometer-core resolved to 1.15.4 via the Micronaut platform BOM 4.10.17, which is affected by the HTTP server instrumentation DoS. The Micronaut platform has no 4.x release shipping a patched micrometer, so pin the two directly declared micronaut-micrometer artifacts to 5.13.3 (same 5.13.x line used by platform 4.10.17), whose BOM manages micrometer 1.15.12. Verified: dependencyInsight now resolves io.micrometer:micrometer-core to 1.15.12 on runtimeClasspath. Addresses CVE-2026-40984 / GHSA-g3pr-3p32-fp23 See: https://github.com/seqeralabs/wave/security/dependabot/74
pditommaso
approved these changes
Aug 31, 2026
Contributor
Author
|
Closing without merging. The only way to reach the patched Micrometer within the current Micronaut line is to pin Deferring this CVE until an upstream platform BOM ships the patched version. The JIRA ticket has been moved out of the active sprint with an updated due date. The branch is retained if we want to revisit. |
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
io.micrometer:micrometer-coreresolved to 1.15.4 onruntimeClasspath, which is affected by the Micrometer HTTP server instrumentation DoS (High, 7.5).It is a transitive dependency:
io.micronaut.platform:micronaut-platform:4.10.17→micronaut-micrometer-bom:5.13.2→micrometer-bom:1.15.4. There is no Micronaut platform 4.x release shipping a patched micrometer (4.10.17 is the latest 4.x; 5.x is a major upgrade out of scope here).Fix: pin the two directly declared
io.micronaut.micrometerartifacts to5.13.3— same 5.13.x line already used by platform 4.10.17, a patch bump — whose BOM managesmicrometer 1.15.12. Noconstraints/resolutionStrategy.forceused.Verification
All micrometer artifacts (
-core,-commons,-observation,-registry-prometheus) now resolve to1.15.12../gradlew compileGroovy compileJavasucceeds.JIRA
COMP-2258: Fix Micrometer HTTP server instrumentations DoS
Security Advisory
🤖 Generated with Claude Code