Vulnerabilities in pkg:golang/github.com/kubetail-org/kubetail/modules/cli

PACKAGE
Advisory Identifier: GHSA-v8j7-hp7c-738f
Advisory Summary

CVE-2026-44514 is a MODERATE (CVSS 6.5) kubetail has a cross-site websocket vulnerability (CWE-1385: Missing Origin Validation in WebSockets) affecting Github.com/kubetail org/kubetail/modules/dashboard libraries in the Go ecosystem. The issue involves kubetail has a cross-site websocket hijacking issue that allows attacker to read kubernetes logs from authenticated users. Remediation is available by upgrading affected packages to version 0.14.0, 0.16.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/kubetail-org/kubetail/modules/cli

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/kubetail-org/kubetail/modules/cli. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-v8j7-hp7c-738f CVE-2026-44514 MODERATE Kubetail has a Cross-Site WebSocket Hijacking issue that allows attacker to read Kubernetes logs from authenticated users

CVE-2026-44514 at a Glance

CVE Identifier CVE-2026-44514
GHSA Identifier GHSA-v8j7-hp7c-738f
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-1385: Missing Origin Validation in WebSockets
Affected Product Github.com/kubetail org/kubetail/modules/dashboard
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-44514

To remediate this vulnerability, upgrade all affected Github.com/kubetail org/kubetail/modules/dashboard dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/kubetail-org/kubetail/modules/dashboard fixed: 0.14.0
Upgrade github.com/kubetail-org/kubetail/modules/dashboard to 0.14.0
github.com/kubetail-org/kubetail/modules/cli fixed: 0.16.0
Upgrade github.com/kubetail-org/kubetail/modules/cli to 0.16.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/kubetail-org/kubetail/modules/dashboard

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-44514, inspect your project dependencies for Github.com/kubetail org/kubetail/modules/dashboard:

inspect dependencies for github.com/kubetail-org/kubetail/modules/dashboard

Analyze the terminal output to locate any version of Github.com/kubetail org/kubetail/modules/dashboard in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.14.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1385: Missing Origin Validation in WebSockets, where the product uses a websocket, but it does not properly verify that the source of data or communication is valid. In Github.com/kubetail org/kubetail/modules/dashboard, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 application code, bearer tokens, internal hostnames, customer PII, and other secrets, so the practical impact of read access can be significant. 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's automatic re-sending of basic-auth credentials on the WebSocket upgrade request enables the same attack against the configured dashboard origin. ### Affected versions | Component | Name | Affected | Patched | | --------------------------------- | ---------------------- | -------- | ---------- | | Kubetail Dashboard docker image | `kubetail-dashboard` | < 0.14.0 | >= 0.14.0 | | Kubetail Helm Chart | `kubetail/kubetail` | < 0.23.0 | >= 0.23.0 | | Kubetail CLI | `kubetail` | < 0.16.0 | >= 0.16.0 | Confirmed in Google Chrome. Microsoft Edge is presumed affected as it shares Chromium's WebSocket implementation, but was not directly tested. **Preconditions for exploitation** 1. The victim has an active authenticated Kubetail session (desktop dashboard running, or browser holding valid credentials for a cluster deployment). 2. The victim visits a web page controlled by the attacker in the same browser. 3. The attacker knows or can guess the dashboard URL (trivial for desktop; cluster deployments require knowing the Ingress hostname). ### Patches Upgrade to: * Kubetail Dashboard 0.14.0 or later * Kubetail Helm Chart 0.23.0 or later * Kubetail CLI 0.16.0 or later ### Workarounds If users cannot upgrade immediately: * **Desktop:** Stop the dashboard (kubetail CLI process) when not actively in use. Avoid visiting untrusted sites in the same browser profile while the dashboard is running. * **Cluster:** Restrict Ingress access to a VPN, bastion, or office network. Add a stronger outer authentication layer (e.g. OAuth proxy) in front of basic auth. Consider browser profile isolation for cluster admins.

CVE-2026-44514 Affected Github.com/kubetail org/kubetail/modules/dashboard Versions

2 component(s)
Fixed Versions:
0.14.00.16.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/kubetail-org/kubetail/modules/dashboard
Go
< 0.14.0
0.14.0
github.com/kubetail-org/kubetail/modules/cli
Go
< 0.16.0
0.16.0

References

Frequently Asked Questions

What is CVE-2026-44514?
CVE-2026-44514 is a security vulnerability in Github.com/kubetail org/kubetail/modules/dashboard involving Kubetail has a Cross-Site WebSocket Hijacking issue that allows attacker to read Kubernetes logs from authenticated users under CWE-1385: Missing Origin Validation in WebSockets.
Which Github.com/kubetail org/kubetail/modules/dashboard versions are affected?
Affected versions include releases prior to 0.14.0, 0.16.0 across affected packages: github.com/kubetail-org/kubetail/modules/dashboard, github.com/kubetail-org/kubetail/modules/cli.
What version fixes CVE-2026-44514?
Upgrading to 0.14.0, 0.16.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/kubetail-org/kubetail/modules/dashboard affected?
Yes, github.com/kubetail-org/kubetail/modules/dashboard is affected in releases prior to 0.14.0. Upgrade your dependency to 0.14.0 or later.
Is github.com/kubetail-org/kubetail/modules/cli affected?
Yes, github.com/kubetail-org/kubetail/modules/cli is affected in releases prior to 0.16.0. Upgrade your dependency to 0.16.0 or later.
What is the CVSS score of CVE-2026-44514?
CVE-2026-44514 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-44514?
CVE-2026-44514 is classified under CWE-1385: Missing Origin Validation in WebSockets (The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid.).
How can I check Go dependencies for CVE-2026-44514?
Run the dependency tree command: 'inspect dependencies for github.com/kubetail-org/kubetail/modules/dashboard'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v8j7-hp7c-738f",
  "modified" : "2026-05-14T20:54:00Z",
  "published" : "2026-05-07T02:34:32Z",
  "aliases" : [ "CVE-2026-44514" ],
  "summary" : "Kubetail has a Cross-Site WebSocket Hijacking issue that allows attacker to read Kubernetes logs from authenticated users",
  "details" : "### Summary\n\nKubetail'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).\n\n### Impact\n\nAn attacker who can convince an authenticated Kubetail user to visit a page they control can:\n\n- Establish a WebSocket connection to the victim's dashboard from the attacker's origin\n- Stream container logs the victim has access to via the Kubernetes API\n- Exfiltrate the contents to an attacker-controlled server\n\nThe 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.\n\nThe 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.\nFor cluster deployments fronted by HTTP basic auth, the browser's automatic re-sending of basic-auth credentials on the WebSocket upgrade request enables the same attack against the configured dashboard origin.\n\n### Affected versions\n\n| Component                                    | Name                           | Affected | Patched   |\n| --------------------------------- | ---------------------- | -------- | ---------- |\n| Kubetail Dashboard docker image | `kubetail-dashboard` | < 0.14.0  | >= 0.14.0  |\n| Kubetail Helm Chart                       | `kubetail/kubetail`       | < 0.23.0 | >= 0.23.0 |\n| Kubetail CLI                                    | `kubetail`                     | < 0.16.0 | >= 0.16.0  |\n\nConfirmed in Google Chrome. Microsoft Edge is presumed affected as it shares Chromium's WebSocket implementation, but was not directly tested.\n\n**Preconditions for exploitation**\n\n1. The victim has an active authenticated Kubetail session (desktop dashboard running, or browser holding valid credentials for a cluster deployment).\n2. The victim visits a web page controlled by the attacker in the same browser.\n3. The attacker knows or can guess the dashboard URL (trivial for desktop; cluster deployments require knowing the Ingress hostname).\n\n### Patches\n\nUpgrade to:\n* Kubetail Dashboard 0.14.0 or later\n* Kubetail Helm Chart 0.23.0 or later\n* Kubetail CLI 0.16.0 or later\n\n### Workarounds\n\nIf users cannot upgrade immediately:\n\n* **Desktop:** Stop the dashboard (kubetail CLI process) when not actively in use. Avoid visiting untrusted sites in the same browser profile while the dashboard is running.\n* **Cluster:** Restrict Ingress access to a VPN, bastion, or office network. Add a stronger outer authentication layer (e.g. OAuth proxy) in front of basic auth. Consider browser profile isolation for cluster admins.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/kubetail-org/kubetail/modules/dashboard"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.14.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/kubetail-org/kubetail/modules/cli"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.16.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/kubetail-org/kubetail/security/advisories/GHSA-v8j7-hp7c-738f"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-44514"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/kubetail-org/kubetail"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1385" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-07T02:34:32Z",
    "nvd_published_at" : "2026-05-14T17:16:23Z"
  }
}