LiveActive security incident?Get immediate response
CVE Record

CVE-2026-40983: Micrometer gRPC server instrumentation DoS vulnerability

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue can let an unauthenticated remote user disrupt affected services by sending specially crafted gRPC requests to software instrumented with vulnerable Micrometer versions. The impact described is availability loss, not data theft or tampering. Business urgency is highest for customer-facing or critical gRPC services using the affected releases.

Executive priority

Treat as a high-priority availability risk for services using Micrometer with gRPC. It does not indicate data compromise, but a successful attack could interrupt critical service delivery. Prioritize exposed production services, then internal systems with important operational dependencies.

Technical view

CVE-2026-40983 affects Micrometer 1.16.0 through 1.16.5 and 1.15.0 through 1.15.11. The CVSS 3.1 vector is 7.5 High, network exploitable, low complexity, no privileges or user interaction, with high availability impact. CWEs are CWE-400 and CWE-770, indicating uncontrolled resource consumption/allocation issues.

Likely exposure

Exposure is likely in Java applications using Micrometer gRPC server instrumentation in the listed 1.15.x or 1.16.x ranges. Internet-facing, partner-facing, or high-volume internal gRPC services carry the most operational risk. The source bundle does not provide CPEs or full product dependency mapping.

Exploitation context

The bundle does not show CISA KEV listing or confirm active exploitation. The vulnerability is remotely reachable under the CVSS vector and requires no privileges or user interaction. Public advisories exist, so defenders should assume awareness is increasing, but exploit availability is not established here.

Researcher notes

The provided data lacks root-cause detail, proof-of-concept status, and explicit fixed versions. Analysis should stay focused on affected Micrometer release ranges, gRPC server instrumentation exposure, and resource-consumption behavior indicated by CWE-400/CWE-770. Do not infer broader Spring ecosystem impact without vendor confirmation.

Mitigation direction

  • Check Spring advisory for official fixed Micrometer versions and upgrade guidance.
  • Check Red Hat errata for affected packaged products and supported updates.
  • Update dependency constraints to avoid Micrometer 1.16.0-1.16.5 and 1.15.0-1.15.11.
  • Prioritize remediation for reachable gRPC services handling critical transactions.
  • Monitor service availability and resource exhaustion signals during remediation.

Validation and detection

  • Inventory applications using Micrometer gRPC server instrumentation.
  • Inspect build files and dependency lockfiles for affected Micrometer versions.
  • Map affected services to exposed gRPC endpoints and business criticality.
  • Confirm vendor advisory status before declaring a version remediated.
  • Validate deployed artifacts no longer contain affected dependency ranges.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-40983 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6vmware
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-40983Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPmicrometer: micrometer-core: Micrometer: Denial of Service via specially crafted gRPC requests
other:Red Hat severity ratingcvssV3_1
  • 2026-06-09T05:00:52.290Z: Reported to Red Hat.
  • 2026-06-09T03:46:54.131Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SpringMicrometer1.16.0, 1.15.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.