{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-56150 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56150 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56150 is a medium-severity denial of service vulnerability in Elastic Fleet Server, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56150 and fix it if it is affected.\n\nWhat it is: CVE-2026-56150 is a medium-severity denial of service vulnerability in Elastic Fleet Server, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-56150 in the wild and no public exploit code.\n\nAffected product: Elastic Fleet Server. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-56150/ (Markdown: https://insights.sbomify.com/CVE-2026-56150/index.md)","id":"CVE-2026-56150","markdown":"https://insights.sbomify.com/CVE-2026-56150/index.md","name":"CVE-2026-56150","record":{"aliases":["GHSA-w52p-h72q-gcpf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Elastic Fleet Server","requires_auth":"low_privilege","summary":"An attacker can cause a denial of service in Elastic Fleet Server by submitting crafted requests to an upload endpoint, leading to excessive memory consumption.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"fleet_server","vendor":"elastic"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Allocation of Resources Without Limits or Throttling in Fleet Server Leading to Denial of Service","id":"CVE-2026-56150","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Input Validation in Kibana Leading to Denial of Service","id":"CVE-2026-56151"},"packages":[],"prev":{"headline":"Allocation of Resources Without Limits or Throttling in Elasticsearch Leading to Denial of Service","id":"CVE-2026-56149"},"products":["Fleet Server"],"published":"2026-07-01","related":[{"cvss_score":8.1,"headline":"Fleet Server Insertion of Sensitive Information into Log File","id":"CVE-2023-46667","kev_date_added":null,"published":"2023-10-26"},{"cvss_score":6.5,"headline":"Authorization Bypass Through User-Controlled Key in Fleet Server Leading to Information Disclosure","id":"CVE-2026-72657","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":3.1,"headline":"Incorrect Authorization in Fleet Server Leading to Denial of Service of Agent Upload Operations","id":"CVE-2026-78587","kev_date_added":null,"published":"2026-09-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-01","vendors":["Elastic"]},"summary":"An attacker can cause a denial of service in Elastic Fleet Server by submitting crafted requests to an upload endpoint, leading to excessive memory consumption.","url":"https://insights.sbomify.com/CVE-2026-56150/"}