Kubetail has a Cross-Site WebSocket Hijacking issue that allows attacker to read Kubernetes logs from authenticated users
CVE-2026-44514GHSA-v8j7-hp7c-738f
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/kubetail-org/kubetail/modules/dashboard 0.14.0; github.com/kubetail-org/kubetail/modules/cli 0.16.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/kubetail-org/kubetail/modules/dashboard
- Affected
- < 0.14.0
- Fixed in
- 0.14.0
Go github.com/kubetail-org/kubetail/modules/cli
- Affected
- < 0.16.0
- Fixed in
- 0.16.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-v8j7-hp7c-738f lists affected ranges: Go github.com/kubetail-org/kubetail/modules/dashboard >=0 =0 <0.16.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-44514: 0.17% estimated exploitation activity in the next 30 days; percentile 6.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Kubetail'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'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). Impact An attacker who can convince an authenticated Kubetail user to visit a page they control can: - Establish a WebSocket connection to the victim's dashboard from the attacker's origin - Stream container logs the victim has access to via the Kubernetes API - Exfiltrate the contents to an attacker-controlled server The attacker gains read-only access to logs — no write or destructive operations are exposed. However, container logs frequently contain credentials accidentally written by…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-v8j7-hp7c-738f
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-44514 Advisory: Kubetail has a Cross-Site WebSocket Hijacking issue that allows attacker to read Kubernetes logs from authenticated users IDs: CVE-2026-44514, GHSA-v8j7-hp7c-738f Record: https://patchnext.com/advisories/cve-2026-44514 (revision 1, source checked 26 Oct 2026, 15:22 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/kubetail-org/kubetail/modules/dashboard 0.14.0; github.com/kubetail-org/kubetail/modules/cli 0.16.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/kubetail-org/kubetail/modules/dashboard: affected < 0.14.0; fixed in 0.14.0 - Go github.com/kubetail-org/kubetail/modules/cli: affected < 0.16.0; fixed in 0.16.0 ## Suggested inspection (read-only) - Go github.com/kubetail-org/kubetail/modules/dashboard: check the installed version with your package manager. - Go github.com/kubetail-org/kubetail/modules/cli: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/kubetail-org/kubetail/modules/dashboard, github.com/kubetail-org/kubetail/modules/cli. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-v8j7-hp7c-738f (GitHub-reviewed advisory GHSA-v8j7-hp7c-738f lists affected ranges: Go github.com/kubetail-org/kubetail/modules/dashboard >=0 =0 <0.16.0) Commands are suggestions: review each one before running it.
Loading voting…