Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Go HTTP file-serving endpoint
-
DeliveryCraft Range header with many small ranges
-
ExploitTrigger excessive CPU in range parser
-
ExecutionRepeat/scale requests
-
ImpactExhaust server CPU, deny 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 | Exploitation requires that the target server use the net/http file-serving handlers FileServer, ServeContent, or ServeFile(FS) - these must be exposed and reachable for the Range-header parsing path to be triggered; a Go application that does not serve files via these handlers is not affected by this specific vector. The trigger is a single HTTP request carrying a Range header enumerating a large number of small ranges. Per the CVSS vector (PR:N/UI:N) no authentication or user interaction is needed, and default configurations are affected wherever these handlers are used. The limiting factor is the handler/feature dependency plus the affected version range (net/http before 1.26.9, and 1.27.0-0 before 1.27.2); impact is availability-only (CPU exhaustion), with no data compromise. |
| Impact | This is a resource-exhaustion denial-of-service in the Go standard library's net/http package (CWE-770, uncontrolled resource consumption). The CVSS 7.5 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) indicates a network-reachable, low-complexity, unauthenticated attack with impact confined to availability only - no confidentiality or integrity exposure. Signals are internally consistent but point to a moderate, not emergency, priority: EPSS is very low at 0.17% (6th percentile), the CVE is NOT on CISA KEV, and CISA SSVC records Exploitation as 'none' with Technical Impact 'partial' - meaning no observed exploitation and only partial (availability-degrading) impact, not full system takeover. The one amplifying signal is SSVC Automatable=yes, which fits a trivially scriptable Range-header flood. No public POC is referenced in the provided data. Net read: a legitimately exploitable, easy-to-trigger DoS against any Go HTTP server using the affected file-serving handlers, but the 7.5 'High' score overstates urgency relative to real-world exploitation evidence - this is a patch-in-normal-cycle issue absent exposure of a critical internet-facing Go service. Note the tension: high-and-automatable CVSS/SSVC versus near-zero EPSS and no KEV listing suggests broad patching will outpace any widespread exploitation. |
| Exploit ScenarioDerived | An unauthenticated remote attacker sends HTTP requests to a Go web server whose handlers use FileServer, ServeContent, or ServeFile, each request carrying a Range header specifying a very large number of small byte ranges. The server spends excessive CPU parsing and servicing these ranges, and a modest volume of such requests degrades or exhausts server capacity, denying service to legitimate users. No authentication or user interaction is required and the attack is trivially automatable; no public exploit code is referenced in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
CPU exhaustion in the Go standard library's net/http file-serving handlers (FileServer, ServeContent, and ServeFile(FS)) lets remote unauthenticated attackers degrade or deny service by sending a single HTTP request whose Range header enumerates a large number of small ranges. The flaw affects net/http in Go releases before 1.26.9 and 1.27.0-0 before 1.27.2, but only on servers that actually expose those file-serving handlers; default configurations that use them are affected with no authentication or user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Impact is availability-only, exploitation is not confirmed and no public exploit has been identified at time of analysis, EPSS is low at 0.17% (6th percentile), and patched releases are available from the vendor.
RemediationAI
Vendor-released patch: upgrade to Go 1.26.9 or to 1.27.2 (i.e., move off the pre-1.26.9 and 1.27.0-0 <1.27.2 ranges) and rebuild affected binaries, since net/http is compiled into the resulting artifact - details are in the upstream record at https://pkg.go.dev/vuln/GO-2026-6609 and the fix at https://go.dev/cl/847309. Where immediate rebuilding is not possible, place an edge proxy or middleware in front of file-serving endpoints that rejects Range headers with more than a small number of ranges or with abnormally long byte-range lists, accepting that legitimate multi-range clients such as document viewers may see failures; alternatively strip the Range header entirely, which disables HTTP 206 partial content and breaks resumable downloads and media seeking. Rate limiting or per-connection concurrency caps on file-serving routes reduces the practical amplification of many concurrent malicious requests, and applying bounded server timeouts gives partial protection, though neither removes the per-request CPU burn from a single crafted Range header. If file serving is not a required function, disabling static file handlers for untrusted clients removes the vulnerable code path entirely at the cost of that feature.
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
The affected component is the net/http package in the Go standard library, identified by CPE cpe:2.3:a:go_standard_library:net/http:*:*:*:*:*:*:*:*. Root cause is CWE-770 (Allocation of Resources Without Limits or Throttling): the Range header parser and the multipart-range handling inside FileServer, ServeContent, and ServeFile(FS) do not bound the number of ranges a client may request, so a crafted header enumerating many small ranges drives disproportionate CPU work per request while the attacker spends negligible bandwidth. This is a classic algorithmic-complexity / uncontrolled-resource-consumption denial of service rather than memory corruption or injection: the CVSS vector shows scope unchanged, confidentiality and integrity impact none, and availability impact high, with PR:N/UI:N meaning no privileges or interaction are needed. Because net/http ships inside the Go toolchain, exposure depends on how applications are built - any binary compiled with an affected Go version and serving files through the listed handlers inherits the behaviour. CISA's SSVC assessment rates exploitation as none, automatable as yes, and technical impact as partial, which matches a low-sophistication, high-repeatability availability attack rather than a data-compromising one.
Know when Net Http 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
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Remote, unauthenticated, single-request trigger against default file-serving handlers gives AV:N/AC:L/PR:N/UI:N; CPU-exhaustion DoS yields A:H with no C/I impact.
Primary rating from Vendor (Go).
CVSS VectorVendor: Go
Lifecycle Timeline
3DescriptionCVE.org
When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU.
Executive ViewAI
Go-based applications that publicly serve files through the net/http FileServer, ServeContent, or ServeFile(FS) handlers are exposed to a remote, unauthenticated CPU-exhaustion attack that can degrade or deny service. While there is no public exploit identified at time of analysis and a vendor patch is available, the organizational risk is concentrated in internet-facing Go services, where a single request can cause availability loss. Leadership should care because customer-facing or internal file-serving endpoints may become unavailable, and prompt remediation is required to prevent operational disruption.
Apply vendor patch.
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
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Remote denial of service in Go's HTTP/2 stack (both golang.org/x/net/http2 and the net/http standard library) allows an
Signals conflict: the original CVSS rates integrity and availability impact as high (9.1), but independent assessment de
Response smuggling is possible in Go's HTTP/2 implementation (net/http and golang.org/x/net/http2) when a program acts a
Request smuggling in the Go net/http standard library occurs when an application handler answers an HTTP/1 CONNECT reque
EUVD-2026-95424
GHSA-f4xw-m386-m277
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB