https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 19:57:10 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-319108 EUVD-2026-319108 https://cve.radiocsirt.org/vuln/euvd-2026-319108 https://cve.radiocsirt.org/vuln/fkie_cve-2026-44514 <p>Kubetail is a real-time logging dashboard for Kubernetes. Prior to 0.14.0, Kubetail&#39;s dashboard exposes WebSocket endpoints that did not adequately validate the Origin header on connection upgrade. A malicious web page visited by a user with an active Kubetail session could open a WebSocket to the user&#39;s dashboard and read their Kubernetes logs in real time. This is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability and affects both the desktop deployment (default http://localhost:7500) and cluster deployments (typically behind an Ingress with HTTP basic auth). This vulnerability is fixed in 0.14.0.</p> <p>Kubetail is a real-time logging dashboard for Kubernetes. Prior to 0.14.0, Kubetail&#39;s dashboard exposes WebSocket endpoints that did not adequately validate the Origin header on connection upgrade. A malicious web page visited by a user with an active Kubetail session could open a WebSocket to the user&#39;s dashboard and read their Kubernetes logs in real time. This is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability and affects both the desktop deployment (default http://localhost:7500) and cluster deployments (typically behind an Ingress with HTTP basic auth). This vulnerability is fixed in 0.14.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-44514 https://cve.radiocsirt.org/vuln/ghsa-v8j7-hp7c-738f <p><strong>Affected:</strong> Go: github.com/kubetail-org/kubetail/modules/dashboard, Go: github.com/kubetail-org/kubetail/modules/cli</p> <p>### Summary</p> <p>Kubetail&#39;s dashboard exposes WebSocket endpoints that did not adequately validate the Origin header on connection upgrade. A malicious web page visited by a user with an active Kubetail session could open a WebSocket to the user&#39;s dashboard and read their Kubernetes logs in real time. This is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability and affects both the desktop deployment (default http://localhost:7500) and cluster deployments (typically behind an Ingress with HTTP basic auth).</p> <p>### Impact</p> <p>An attacker who can convince an authenticated Kubetail user to visit a page they control can:</p> <p>- Establish a WebSocket connection to the victim&#39;s dashboard from the attacker&#39;s origin - Stream container logs the victim has access to via the Kubernetes API - Exfiltrate the contents to an attacker-controlled server</p> <p>The attacker gains **read-only** access to logs — no write or destructive operations are exposed. However, container logs frequently contain credentials accidentally written by application code, bearer tokens, internal hostnames, customer PII, and other secrets, so the practical impact of read access can be significant.</p> <p>The desktop deployment is particularly exposed because the dashboard is reachable at a predictable localhost URL, requires no network reachability from the attacker, and the browser will attach ambient credentials to the WebSocket handshake. For cluster deployments fronted by HTTP basic auth, the browser&#39;s automatic re-sending of basic-…</p> <p><strong>Affected:</strong> Go: github.com/kubetail-org/kubetail/modules/dashboard, Go: github.com/kubetail-org/kubetail/modules/cli</p> <p>### Summary</p> <p>Kubetail&#39;s dashboard exposes WebSocket endpoints that did not adequately validate the Origin header on connection upgrade. A malicious web page visited by a user with an active Kubetail session could open a WebSocket to the user&#39;s dashboard and read their Kubernetes logs in real time. This is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability and affects both the desktop deployment (default http://localhost:7500) and cluster deployments (typically behind an Ingress with HTTP basic auth).</p> <p>### Impact</p> <p>An attacker who can convince an authenticated Kubetail user to visit a page they control can:</p> <p>- Establish a WebSocket connection to the victim&#39;s dashboard from the attacker&#39;s origin - Stream container logs the victim has access to via the Kubernetes API - Exfiltrate the contents to an attacker-controlled server</p> <p>The attacker gains **read-only** access to logs — no write or destructive operations are exposed. However, container logs frequently contain credentials accidentally written by application code, bearer tokens, internal hostnames, customer PII, and other secrets, so the practical impact of read access can be significant.</p> <p>The desktop deployment is particularly exposed because the dashboard is reachable at a predictable localhost URL, requires no network reachability from the attacker, and the browser will attach ambient credentials to the WebSocket handshake. For cluster deployments fronted by HTTP basic auth, the browser&#39;s automatic re-sending of basic-…</p> https://cve.radiocsirt.org/vuln/ghsa-v8j7-hp7c-738f