Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2026-40984

Uncontrolled Resource Consumption

Published: Jun 09, 2026 | Modified: Aug 06, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-40984
CWEhttps://cwe.mitre.org/data/definitions/400.html

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.

Weakness

The product does not properly control the allocation and maintenance of a limited resource.

Affected Software

NameVendorStart VersionEnd Version
Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16RedHatmicrometer-core*
Red Hat Build of Apache Camel 4.18 for Quarkus 3.33RedHatmicrometer-core*
Red Hat build of Keycloak 26.6RedHatrhbk/keycloak-operator-bundle:26.6.5-1*
Red Hat build of Keycloak 26.6RedHatrhbk/keycloak-rhel9:26.6-11*
Red Hat build of Keycloak 26.6RedHatrhbk/keycloak-rhel9-operator:26.6-11*
Red Hat build of Keycloak 26.6.5RedHatmicrometer-core*
Red Hat build of Keycloak 26.6.5RedHatrhbk/keycloak-rhel9*
Red Hat build of Keycloak 26.6.5RedHatrhbk/keycloak-rhel9-operator*
Red Hat build of Keycloak 26.6.5RedHatrhbk-openshift-rhel9/rhbk-openshift-rhel9*
Red Hat build of Keycloak 26.6.5RedHatrhbk-rhel9-operator/rhbk-rhel9-operator*
Red Hat Data Grid 8.6.2RedHatmicrometer-core*

Potential Mitigations

  • Mitigation of resource exhaustion attacks requires that the target system either:

  • The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.

  • The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use