NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2026-40983 — micrometer-core

HIGH

CVE-2026-40983 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in io.micrometer:micrometer-core. A fix is available for io.micrometer:micrometer-core — see the affected versions and patch details below.

Micrometer gRPC server instrumentation DoS

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-40983.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk
0.00%0.45%0.90%1.35%0.5%0.6%Jul 26Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕io.micrometer:micrometer-core☕io.micrometer:micrometer-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.micrometer:micrometer-core≥ 1.16.0&&< 1.16.61.16.6io.micrometer:micrometer-core:1.16.6
☕Mavenio.micrometer:micrometer-core≥ 1.15.0&&< 1.15.121.15.12io.micrometer:micrometer-core:1.15.12

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.micrometer:micrometer-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.micrometer:micrometer-core to 1.16.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40983 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This is an Important denial-of-service vulnerability in Micrometer, as a remote unauthenticated attacker can disrupt the availability of affected systems by sending specially crafted gRPC requests. The broad accessibility of gRPC endpoints in typical deployments contributes to the elevated risk, allowing for…

Workaround published by Red Hat
To mitigate this issue, restrict network access to services exposing Micrometer's gRPC endpoints to trusted clients only. Implement firewall rules to limit inbound connections to the specific ports used by gRPC. If gRPC functionality is not essential for the deployment, consider disabling it entirely to eliminate the attack vector. Any changes to network configurations or service settings may require a service restart to take effect, potentially impacting availability during the transition.
Source: Red Hat security advisory for CVE-2026-40983 (CC BY 4.0)
ProductFixed inAdvisory
AMQ Clients 2026.Q3micrometer-coreRHSA-2026:69459
Red Hat AMQ Broker 7.14.1micrometer-coreRHSA-2026:66488
Red Hat Build of Apache Camel 3.33.2.SP2io.micrometer/micrometer-core:1.16.6.redhat-00001RHSA-2026:36839
Red Hat build of Keycloak 26.6rhbk/keycloak-operator-bundle:26.6.5-1RHSA-2026:50849
Red Hat build of Keycloak 26.6.5micrometer-coreRHSA-2026:50848
Red Hat build of Quarkus 3.33.2.SP2io.micrometer/micrometer-core:1.16.6.redhat-00001RHSA-2026:36013
Red Hat Data Grid 8.6.2micrometer-coreRHSA-2026:41951
Red Hat JBoss Enterprise Application Platform 8.1micrometer-coreRHSA-2026:70421

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-40983 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-40983: micrometer-core DoS — Fixed in 1.16.6