Server restart via unbounded HTTP body reads
Published Mar 27, 2026 · Updated Mar 27, 2026
Resource exhaustion in Fleet before 4.81.0 allows remote attackers to restart the server process with oversized HTTP requests. Multiple unauthenticated HTTP handlers read entire request bodies without a size limit, allowing attacker-controlled payloads to drive memory allocation. No authentication or user interaction is required; the documented impact is memory exhaustion and a Fleet server restart, with no data exposure or integrity impact.
Summary
What happened
Resource exhaustion in Fleet before 4.81.0 allows remote attackers to restart the server process with oversized HTTP requests. Multiple unauthenticated HTTP handlers read entire request bodies without a size limit, allowing attacker-controlled payloads to drive memory allocation. No authentication or user interaction is required; the documented impact is memory exhaustion and a Fleet server restart, with no data exposure or integrity impact.
The record
- CVE
- CVE-2026-26061
- Published
- Mar 27, 2026
- Updated
- Mar 27, 2026
- Vendor
- Fleet Device Management
- Product
- Fleet
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2026CVE publishedPublication date reported by the CVE source.
- Mar 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.81.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo