CVE-2026-26061: Fleet's unbounded request body read allows remote Denial of Service

Published Mar 27, 2026
·
Updated

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

Credits

Fleet thanks @fuzzztf for responsibly reporting this issue.

Other sources

Fleet is open source device management software. Prior to 4.81.0, 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. Version 4.81.0 patches the issue.

MITRE

Affected Software

2 affected componentsFixes available
go/github.com/fleetdm/fleet/v4<4.43.5-0.20260113202849-bbc1aef2987d
4.43.5-0.20260113202849-bbc1aef2987d
fleetdm fleet<4.81.0

Event History

Mar 27, 2026
Advisory Published
via GitHub·06:17 PM
Data Sourced
via GitHub·06:17 PM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·06:23 PM
Data Sourced
via MITRE·06:23 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-26061?

CVE-2026-26061 is classified as a denial of service vulnerability due to its potential to crash services by overwhelming them with large payloads.

2

How do I fix CVE-2026-26061?

To fix CVE-2026-26061, update Fleet to version 4.43.5-0.20260113202849-bbc1aef2987d or later, where the issue has been addressed.

3

What kind of attacks can CVE-2026-26061 facilitate?

CVE-2026-26061 can facilitate denial of service attacks by allowing attackers to send unbounded request bodies, overwhelming server resources.

4

Which versions of Fleet are affected by CVE-2026-26061?

Versions of Fleet prior to 4.43.5-0.20260113202849-bbc1aef2987d are affected by CVE-2026-26061.

5

Is authentication required to exploit CVE-2026-26061?

No, CVE-2026-26061 can be exploited without authentication, allowing any unauthenticated attacker to trigger the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203