Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend large HTTP payload to unauthenticated endpoint
-
DeliveryServer reads request body without size limit
-
ExploitExcessive memory allocation occurs
-
ExecutionFleet process exhausts available memory
-
ImpactServer restarts causing denial-of-service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions — remote unauthenticated attacker can exploit multiple HTTP endpoints in Fleet server that lack request body size limits by sending large or repeated payloads, causing denial-of-service through memory exhaustion. |
| Impact | Real-world risk is moderate despite the unauthenticated attack surface. The vulnerability explicitly impacts availability only with no data exposure, authentication bypass, or privilege escalation according to the advisory. No CVSS score was provided, limiting quantitative risk comparison, but the unauthenticated nature and low technical complexity suggest a likely CVSS vector similar to AV:N/AC:L/PR:N, indicating network-accessible attack with low barriers. No public exploit identified at time of analysis and no CISA KEV listing indicates this is not being actively exploited in the wild. The practical impact is service disruption rather than compromise, and effective workarounds exist via reverse proxy controls. Organizations using Fleet should prioritize patching based on their service availability requirements and public exposure, but this is not a critical compromise risk comparable to authentication bypass or remote code execution vulnerabilities. |
| Exploit ScenarioDerived | An unauthenticated remote attacker identifies publicly accessible Fleet server endpoints and crafts HTTP POST requests with multi-gigabyte request bodies targeting vulnerable unauthenticated handlers. By sending sustained large requests or parallelizing multiple connections, the attacker forces the Fleet server process to allocate excessive heap memory until exhaustion occurs, triggering an out-of-memory crash and service restart. This creates a sustained denial-of-service condition affecting fleet management operations for connected devices until mitigation controls are deployed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 27, 2026
Fleet server memory exhaustion via unbounded request bodies allows unauthenticated denial-of-service against multiple HTTP endpoints. The vulnerability affects Fleet v4 (github.com/fleetdm/fleet/v4) and was responsibly disclosed by @fuzzztf. Attackers can exhaust available memory and force server restarts by sending oversized or repeated HTTP requests to unauthenticated endpoints lacking size limits. No public exploit identified at time of analysis, though the attack mechanism is straightforward given the CWE-770 resource allocation vulnerability class.
RemediationAI
Upgrade Fleet to the patched version specified in the vendor security advisory at https://github.com/fleetdm/fleet/security/advisories/GHSA-99hj-44vg-hfcp (exact version number not provided in available intelligence). Until patching is possible, implement request body size limits at a reverse proxy or load balancer layer using NGINX, Envoy, or similar with configurations such as client_max_body_size in NGINX. Restrict network access to Fleet endpoints to known IP ranges using firewall rules or network segmentation where operationally feasible. Monitor Fleet server memory usage and process restart frequency for abnormal patterns indicating exploitation attempts. For questions or incident response assistance, contact Fleet security team at security@fleetdm.com as noted in the advisory.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in go, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability is rooted in CWE-770 (Allocation of Resources Without Limits or Throttling), affecting the Fleet device management platform written in Go. The affected product is identified via CPE as pkg:go/github.com_fleetdm_fleet_v4. The flaw exists in multiple HTTP request handlers that fail to enforce maximum body size limits when processing incoming requests. Without proper resource controls, the Go HTTP server allocates memory proportional to request size, allowing an attacker to consume heap space until the process crashes or is terminated by the operating system. This class of vulnerability is particularly common in Go web applications that use io.ReadAll or similar unbounded readers on request bodies without implementing middleware-level size restrictions or per-handler validation.
Know when Nginx gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Primary rating from Vendor (https://github.com/fleetdm/fleet).
CVSS VectorVendor: https://github.com/fleetdm/fleet
Lifecycle Timeline
2DescriptionCVE.org
Summary
Fleet contained multiple unauthenticated HTTP endpoints that read request bodies without enforcing a size limit. An unauthenticated attacker could exploit this behavior by sending large or repeated HTTP payloads, causing excessive memory allocation and resulting in a denial-of-service (DoS) condition.
Impact
An unauthenticated attacker could cause the Fleet server process to exhaust available memory and restart by sending oversized or repeated HTTP requests to affected endpoints.
This vulnerability impacts availability only. There is:
- No exposure of sensitive data
- No authentication bypass
- No privilege escalation
- No integrity impact
Workarounds
If upgrading immediately is not possible, the following mitigations can reduce exposure:
- Apply request body size limits at a reverse proxy or load balancer (e.g., NGINX, Envoy).
- Restrict network access to endpoints to known IP ranges where feasible.
- Monitor memory usage and restart frequency for abnormal patterns.
For More Information
If there are any questions or concerns about this advisory, please contact us at:
Email Fleet at [security@fleetdm.com](mailto:security@fleetdm.com)
Credits
Fleet thanks @fuzzztf for responsibly reporting this issue.
Executive ViewAI
Fleet v4 server deployments are vulnerable to denial-of-service attacks through unbounded HTTP request handling, allowing unauthenticated attackers to exhaust server memory and force restarts without authentication credentials. Organizations running Fleet as an endpoint management platform face potential service disruption and operational downtime if the vulnerability is exploited, impacting visibility and control over managed endpoints.
Implement Web Application Firewall (WAF) rules enforcing strict request body size limits (recommend 1-5 MB maximum) on unauthenticated endpoints (/api/v1/osquery/*, /api/v1/fleet/*, etc.); enable HTTP rate limiting per source IP; place Fleet server behind reverse proxy with request filtering; segment Fleet server network to restrict access to authorized networks only; monitor server memory and CPU metrics with alerting for anomalous exhaustion patterns; schedule regular server restarts as interim mitigation if memory leaks observed. Await vendor-released patch; no current vendor-released patch identified at time of analysis.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
The ngx_http_parse_chunked function in http/ngx_http_parse.c in nginx 1.3.9 through 1.4.0 allows remote attackers to cau
A critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
nginx 0.8.41 through 1.4.3 and 1.5.x before 1.5.7 allows remote attackers to bypass intended restrictions via an unescap
An issue was discovered on GL.iNet devices before version 4.5.0. Rated critical severity (CVSS 9.8), this vulnerability
Nginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range fi
The resolver in nginx before 1.8.1 and 1.9.x before 1.9.10 allows remote attackers to cause a denial of service (invalid
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. Rated critical severity (CVSS 9.8
The STARTTLS implementation in mail/ngx_mail_smtp_handler.c in the SMTP proxy in nginx 1.5.x and 1.6.x before 1.6.1 and
Same technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: High| Product | Status |
|---|---|
| openSUSE Leap 15.6 | Fixed |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Fixed |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Fixed |
| openSUSE Leap 15.5 | Fixed |
EUVD-2026-16744
GHSA-99hj-44vg-hfcp
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB