VulnerabilityPublished 14 May 2026Updated 16 May 2026

CVE-2026-44514: kubetail · Missing Origin Validation in WebSockets

Affects kubetailSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.14.0 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.14.0, 0.16.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade kubetail and github.com/kubetail-org/kubetail/modules/dashboard and kubetail-org/kubetail to 0.14.0; github.com/kubetail-org/kubetail/modules/cli to 0.16.0.

Affected software

Product	Affected	Fixed in
kubetail-orgkubetail	Affected <0.14.0	Fixed in 0.14.0
kubetail-orggithub.com/kubetail-org/kubetail/modules/cli	Affected <0.16.0	Fixed in 0.16.0
kubetail-orggithub.com/kubetail-org/kubetail/modules/dashboard	Affected <0.14.0	Fixed in 0.14.0
GitHubkubetail-org/kubetail`pkg:github/kubetail-org/kubetail`Other threats	Affected <0.14.0	Fixed in 0.14.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Kubetail to version 0.14.0 or later, where the missing Origin header validation on WebSocket endpoints has been fixed. No other mitigations are indicated or necessary once the upgrade is applied.

Description

Kubetail versions prior to 0.14.0 have a Cross-Site WebSocket Hijacking (CSWSH) vulnerability due to missing Origin header validation on WebSocket endpoints in its real-time logging dashboard. This flaw allows a malicious web page visited by a user with an active Kubetail session to open a WebSocket connection to the dashboard and read Kubernetes logs in real time. The vulnerability affects both desktop and cluster deployments. The issue is fixed in version 0.14.0.

Impact

An attacker can exploit this vulnerability to read Kubernetes logs in real time from a user's active Kubetail session by leveraging a malicious web page. This compromises the confidentiality of potentially sensitive log data. The vulnerability does not affect integrity or availability. The CVSS 3.1 base score is 6.5 (medium severity), reflecting network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, high confidentiality impact, and no integrity or availability impact.

CWE-1385Missing Origin Validation in WebSockets (opens in a new tab)
Variant weakness
The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid.
Implementation
Enable CORS-like access restrictions by verifying the 'Origin' header during the WebSocket handshake.
Implementation
Use a randomized CSRF token to verify requests.
Implementation
Use TLS to securely communicate using 'wss' (WebSocket Secure) instead of 'ws'.
OWASP ASVS 4.0.3
V14.5.2 (opens in a new tab)
V14.5.3 (opens in a new tab)
V1.4.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/kubetail-org/kubetail/security/advisories/GHSA-v8j7-hp7c-738f (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 May 2026, 15:32 UTC

WeaknessesCWE-1385

Technical details

References

Community reviews

Related threats