https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 13 Nov 2026 04:48:20 +0000 https://db.gcve.eu/vuln/cleanstart-2026-it15296 <p><strong>Affected:</strong> CleanStart: knative-serving, CleanStart: kube-state-metrics, CleanStart: knative-net-istio, CleanStart: rundeck, CleanStart: keda, CleanStart: restic, CleanStart: wait-for-port</p> <p>CVE-2026-97054 affects multiple packages. For HTTP/1 servers, when MaxBytesReader&#39;s limit is exceeded, &#34;Connection: close&#34; header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. See references for individual vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: knative-serving, CleanStart: kube-state-metrics, CleanStart: knative-net-istio, CleanStart: rundeck, CleanStart: keda, CleanStart: restic, CleanStart: wait-for-port</p> <p>CVE-2026-97054 affects multiple packages. For HTTP/1 servers, when MaxBytesReader&#39;s limit is exceeded, &#34;Connection: close&#34; header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. See references for individual vulnerability details.</p> https://db.gcve.eu/vuln/cleanstart-2026-it15296 https://db.gcve.eu/vuln/fkie_cve-2026-97054 <p>For HTTP/1 servers, when MaxBytesReader&#39;s limit is exceeded, &#34;Connection: close&#34; 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.</p> <p>For HTTP/1 servers, when MaxBytesReader&#39;s limit is exceeded, &#34;Connection: close&#34; 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.</p> https://db.gcve.eu/vuln/fkie_cve-2026-97054 https://db.gcve.eu/vuln/ghsa-rg98-f588-44xg <p>For HTTP/1 servers, when MaxBytesReader&#39;s limit is exceeded, &#34;Connection: close&#34; 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.</p> <p>For HTTP/1 servers, when MaxBytesReader&#39;s limit is exceeded, &#34;Connection: close&#34; 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.</p> https://db.gcve.eu/vuln/ghsa-rg98-f588-44xg https://db.gcve.eu/vuln/opensuse-su-2026:12529-1 <p>go1.26-1.26.11-1.1 on GA media</p> <p>go1.26-1.26.11-1.1 on GA media</p> https://db.gcve.eu/vuln/opensuse-su-2026:12529-1 https://db.gcve.eu/vuln/ubuntu-cve-2026-97054 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: golang-1.10, Ubuntu:16.04:LTS: golang-1.10, Ubuntu:16.04:LTS: golang-1.6, Ubuntu:Pro:16.04:LTS: golang-1.13, Ubuntu:Pro:16.04:LTS: golang-1.18, Ubuntu:18.04:LTS: golang-1.10, Ubuntu:Pro:18.04:LTS: golang-1.13, Ubuntu:Pro:18.04:LTS: golang-1.16, Ubuntu:Pro:18.04:LTS: golang-1.18, Ubuntu:18.04:LTS: golang-1.8 and 30 more</p> <p>For HTTP/1 servers, when MaxBytesReader&#39;s limit is exceeded, &#34;Connection: close&#34; 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.</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: golang-1.10, Ubuntu:16.04:LTS: golang-1.10, Ubuntu:16.04:LTS: golang-1.6, Ubuntu:Pro:16.04:LTS: golang-1.13, Ubuntu:Pro:16.04:LTS: golang-1.18, Ubuntu:18.04:LTS: golang-1.10, Ubuntu:Pro:18.04:LTS: golang-1.13, Ubuntu:Pro:18.04:LTS: golang-1.16, Ubuntu:Pro:18.04:LTS: golang-1.18, Ubuntu:18.04:LTS: golang-1.8 and 30 more</p> <p>For HTTP/1 servers, when MaxBytesReader&#39;s limit is exceeded, &#34;Connection: close&#34; 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.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-97054 https://db.gcve.eu/vuln/wid-sec-w-2026-4370 <p>Ein Angreifer kann mehrere Schwachstellen in Golang Go ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Golang Go ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://db.gcve.eu/vuln/wid-sec-w-2026-4370