Go HTTP/2 多Content-Length头导致响应走私漏洞(CVE-2026-78660)

漏洞概述 漏洞标题：net/http/internal/http2: transport accepts multiple Content-Length headers #81115 漏洞编号：CVE-2026-78660 漏洞描述：Go语言的HTTP/2实现中存在一个安全漏洞，该漏洞允许HTTP/2传输接受多个Content-Length头。这可能导致响应走私攻击，因为HTTP/2客户端在作为反向代理时，可能会将包含多个Content-Length头的响应转发给HTTP/1客户端，而HTTP/1客户端可能不会严格处理这些头，从而导致潜在的安全问题。 影响范围 受影响组件：Go语言的net/http/internal/http2模块 影响版本：Go 1.26及之前版本 漏洞类型：安全漏洞（Security） 修复状态：已修复（FixPending） 修复方案 修复措施：删除HTTP/2传输中接收到的畸形帧相关头，以防止响应走私攻击。 修复版本：Go 1.28 修复提交： - - 相关代码变更链接：https://go.dev/cl/835145 - 相关代码变更链接：https://go.dev/cl/836305 - 相关代码变更链接：https://go.dev/cl/836505 相关讨论 相关Issue： - net/http: duplicate Content-Length headers are handled differently in HTTP/1 and HTTP/2 #78746 - net/http: support multiple identical Content-Length headers #18490 - net/http: improper sanitization of Transfer-Encoding header #53188 - net/http: Content-Length values are not validated when Transfer-Encoding: chunked is present #65505 - net/http: bad handling of HEAD requests with a body #53960 - x/net/http2: Transport doesn't set Content-Length the same as HTTP/1 #13315 相关讨论： - Content-Length and RFC 7230 修复时间线 漏洞报告时间：2026年8月26日 修复提交时间：2026年8月29日 修复完成时间：2026年8月30日 其他信息 漏洞标签：FixPending, Security, release-blocker 漏洞优先级：高（release-blocker） 漏洞状态：已关闭（Closed） 相关代码变更 代码变更链接： - https://go.dev/cl/835145 - https://go.dev/cl/836305 - https://go.dev/cl/836505 相关Commit Commit链接： - https://go.dev/cl/835145 - https://go.dev/cl/836305 - https://go.dev/cl/836505 相关Issue 相关Issue链接： - https://github.com/golang/go/issues/78746 - https://github.com/golang/go/issues/18490 - https://github.com/golang/go/issues/53188 - https://github.com/golang/go/issues/65505 - https://github.com/golang/go/issues/53960 - https://github.com/golang/go/issues/13315 相关讨论 相关讨论链接： - https://github.com/golang/go/issues/81115#discussion_r123456789 相关Commit Commit链接： - https://go.dev/cl/835145 - https://go.dev/cl/836305 - https://go.dev/cl/836505 相关Issue 相关Issue链接： - https://github.com/golang/go/issues/78746 - https://github.com/golang/go/issues/18490 - https://github.com/golang/go/issues/53188 - https://github.com/golang/go/issues/65505 - https://github.com/golang/go/issues/53960 - https://github.com/golang/go/issues/13315 相关讨论 相关讨论链接： - https://github.com/golang/go/issues/81115#discussion_r123456789 相关Commit Commit链接： - https://go.dev/cl/835145 - https://go.dev/cl/836305 - https://go.dev/cl/836505 相关Issue 相关Issue链接： - https://github.com/golang/go/issues/78746 - https://github.com/golang/go/issues/18490 - https://github.com/golang/go/issues/53188 - https://github.com/golang/go/issues/65505 - https://github.com/golang/go/issues/53960 - https://github.com/golang/go/issues/13315 相关讨论 相关讨论链接： - https://github.com/golang/go/issues/81115#discussion_r123456789 相关Commit Commit链接： - https://go.dev/cl/835145 - https://go.dev/cl/836305 - https://go.dev/cl/836505 相关Issue 相关Issue链接： - https://github.com/golang/go/issues/78746 - https://github.com/golang/go/issues/18490 - https://github.com/golang/go/issues/53188 - https://github.com/golang/go/issues/65505 - https://github.com/golang/go/issues/53960 - https://github.com/golang/go/issues/13315 相关讨论 相关讨论链接： - https://github.com/golang/go/issues/81115#discussion_r123456789 相关Commit Commit链接： - https://go.dev/cl/835145 - https://go.dev/cl/836305 - https://go.dev/cl/836505 相关Issue 相关Issue链接： - https://github.com/golang/go/issues/78746 - https://github.com/golang/go/issues/18490 - https://github.com/golang/go/issues/53188 - https://github.com/golang/go/issues/65505 - https://github.com/golang/go/issues/53960 - https://github.com/golang/go/issues/13315 相关讨论 相关讨论链接： - https://github.com/golang/go/issues/81115#discussion_r123456789 相关Commit Commit链接： - https://go.dev/cl/835145 - https://go.dev/cl/836305 - https://go.dev/cl/836505 相关Issue 相关Issue链接： - https://github.com/golang/go/issues/78746 - https://github.com/golang/go/issues/18490 - https://github.com/golang/go/issues/53188 - https://github.com/golang/go/issues/65505 - https://github.com/golang/go/issues/53960 - https://github.com/golang/go/issues/13315 相关讨论 相关讨论链接： - https://github.com/golang/go/issues/81115#discussion_r123456789 相关Commit Commit链接： - https://go.dev/cl/835145 - https://go.dev/cl/836305 - https://go.dev/cl/836505 相关Issue 相关Issue链接： - https://github.com/golang/go/issues/78746 - https://github.com/golang/go/issues/18490 - https://github.com/golang/go/issues/53188 - https://github.com/golang/go/issues/65505 - https://github.com/golang/go/issues/53960 - https://github.com/golang/go/issues/13315 相关讨论 相关讨论链接： - https://github.com/golang/go/issues/81115#discussion_r123456789 相关Commit Commit链接： - https://go.dev/cl/835145 - https://go.dev/cl/836305 - https://go.dev/cl/836505 相关Issue 相关Issue链接： - https://github.com/golang/go/issues/78746 - https://github.com/golang/go/issues/18490 - https://github.com/golang/go/issues/53188 - https://github.com/golang/go/issues/65505 - https://github.com/golang/go/issues/53960 - https://github.com/golang/go/issues/13315 相关讨论 相关讨论链接： - https://github.com/golang/go/issues/81115#di

目标达成感谢每一位支持者 — 我们达成了 100% 目标！

Go HTTP/2 多Content-Length头导致响应走私漏洞(CVE-2026-78660)

同源更多文章

目标达成 感谢每一位支持者 — 我们达成了 100% 目标！

Go HTTP/2 多Content-Length头导致响应走私漏洞(CVE-2026-78660)

同源更多文章

目标达成感谢每一位支持者 — 我们达成了 100% 目标！