UBUNTU-CVE-2026-97054: Medium severity ubuntu/golang-1.10 vulnerability

Published Nov 12, 2026
·
Updated

For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header.

Affected Software

24 affected components
ubuntu/golang-1.10*
ubuntu/golang-1.10*
ubuntu/golang-1.6*
ubuntu/golang-1.13*
ubuntu/golang-1.18*
ubuntu/golang-1.10*
ubuntu/golang-1.13*
ubuntu/golang-1.16*
ubuntu/golang-1.18*
ubuntu/golang-1.8*
ubuntu/golang-1.13*
ubuntu/golang-1.16*
ubuntu/golang-1.18*
ubuntu/golang-1.22*
ubuntu/golang-1.17*
ubuntu/golang-1.22*
ubuntu/golang-1.24*
ubuntu/golang-1.13*
ubuntu/golang-1.21*
ubuntu/golang-1.22*
ubuntu/golang-1.24*
ubuntu/golang-1.26*
ubuntu/golang-1.23*
ubuntu/golang-1.24*

Event History

Nov 12, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this issue?

HTTP/1 servers are affected when they use MaxBytesReader or MaxBytesHandler and the handler concurrently reads the request body while writing response headers. The listed Ubuntu golang packages are golang-1.6, golang-1.8, golang-1.10, golang-1.13, golang-1.16, golang-1.18, golang-1.22, and golang-1.24.

2

What must occur for an attacker to trigger the crash?

The request body must exceed the MaxBytesReader limit while the server handler is reading that body concurrently with writing the response header. This can race with the automatic setting of the Connection: close header and cause a runtime panic.

3

Is a default HTTP/1 server configuration affected?

The available information only identifies servers that use MaxBytesReader or MaxBytesHandler in a handler pattern that concurrently reads the request body and writes response headers. It does not establish that default server configurations are affected.

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