Skip to content

fix(deps): upgrade micronaut-micrometer to 5.13.3 (COMP-2257) - #1123

Closed
cristianrcv wants to merge 1 commit into
masterfrom
fix/COMP-2257-micrometer-grpc-dos
Closed

fix(deps): upgrade micronaut-micrometer to 5.13.3 (COMP-2257)#1123
cristianrcv wants to merge 1 commit into
masterfrom
fix/COMP-2257-micrometer-grpc-dos

Conversation

@cristianrcv

Copy link
Copy Markdown
Contributor

Summary

  • Pins the directly declared io.micronaut.micrometer:micronaut-micrometer-core and micronaut-micrometer-registry-prometheus to 5.13.3 (previously version-managed by the Micronaut platform BOM 4.10.17).
  • Micronaut platform 4.10.17 — the newest 4.x release — pins Micrometer 1.15.4, which is vulnerable. micronaut-micrometer 5.13.3 ships Micrometer 1.15.12, the patched release.
  • Verified with ./gradlew dependencyInsight --dependency micrometer-core --configuration runtimeClasspathio.micrometer:micrometer-core:1.15.12, and ./gradlew compileGroovy compileJava passes.
  • Resolves CVE-2026-40983 / GHSA-w737-wx49-qj23 (Micrometer gRPC server instrumentation DoS, High 7.5).

JIRA

COMP-2257: Fix Micrometer gRPC server instrumentation DoS

Security Advisory

https://github.com/seqeralabs/wave/security/dependabot/73

🤖 Generated with Claude Code

The Micronaut platform BOM 4.10.17 pins Micrometer 1.15.4, which is
affected by the gRPC server instrumentation DoS. Pinning the directly
declared micronaut-micrometer artifacts to 5.13.3 brings in the patched
Micrometer 1.15.12.

Addresses CVE-2026-40983 / GHSA-w737-wx49-qj23
See: https://github.com/seqeralabs/wave/security/dependabot/73
@pditommaso

Copy link
Copy Markdown
Collaborator

Duplicate of #1124 ?

@cristianrcv

Copy link
Copy Markdown
Contributor Author

Closing without merging.

The only way to reach the patched Micrometer within the current Micronaut line is to pin io.micronaut.micrometer ahead of the platform BOM. Per repo convention a dependency version comes either from the version catalog or transitively from the BOM — we do not carry a pin ahead of the BOM.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants