Skip to content

← Public intelligence

Maven package

io.micrometer:micrometer-core

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5MavenPublished

    Micrometer HTTP server instrumentations DoS

    CVE-2026-40984 · GHSA-g3pr-3p32-fp23

    Affected
    • Maven io.micrometer:micrometer-core >= 1.16.0, <= 1.16.5; >= 1.15.0, <= 1.15.11; >= 1.14.0, <= 1.14.14; >= 1.10.0, <= 1.13.15; <= 1.9.17
    Fixed in
    1.15.121.16.6· Partial vendor fix
    Issue
    In Micrometer, it is possible for a user to provide specially crafted HTTP requests that may cause a denial-of-service (DoS) condition. Affected versions: micrometer-core 1.16.0 through 1.16.5; 1.15.0 through 1.15.11; 1.14.0 through 1.14.15; 1.13.0 through 1.13.18; 1.9.0 through 1.9.17. micrometer-jetty11 1.16.0 through 1.16.5; 1.15.0 through 1.15.11; 1.14.0 through 1.14.15; 1.13.0 through 1.13.18. micrometer-jetty12 1.16.0 through 1.16.5; 1.15.0 through 1.15.11; 1.14.0 through 1.14.15; 1.13.0 through 1.13.18.

    Recommended action: Upgrade to 1.16.6 or 1.15.12 by release line; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5MavenPublished

    Micrometer gRPC server instrumentation DoS

    CVE-2026-40983 · GHSA-w737-wx49-qj23

    Affected
    • Maven io.micrometer:micrometer-core >= 1.16.0, <= 1.16.5; >= 1.15.0, <= 1.15.11
    Fixed in
    1.15.121.16.6· Vendor fix available
    Issue
    In Micrometer, it is possible for a user to provide specially crafted gRPC requests that may cause a denial-of-service (DoS) condition. Affected versions: Micrometer 1.16.0 through 1.16.5; 1.15.0 through 1.15.11.

    Recommended action: Upgrade to 1.16.6 or 1.15.12 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →