<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 10:08:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-406999</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-406999</link>
      <description>EUVD-2026-406999</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-406999</guid>
    </item>
    <item>
      <title>fkie_cve-2026-129236</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-129236</link>
      <description>&lt;p&gt;Kubeshark is an eBPF-powered network observability tool for Kubernetes. From 53.1.0 until 53.4.0, the start_kubeshark MCP tool in cmd/mcpRunner.go uses callStartKubeshark to append caller-controlled pod_regex as a bare positional argument to kubeshark tap without a -- end-of-options separator, allowing a value beginning with --set to be parsed as a Helm value override. An attacker who influences tool arguments against kubeshark mcp --allow-destructive can redirect the privileged worker, Hub, and front images through tap.docker.registry and tap.docker.tag to an attacker-controlled registry. Because the deployed worker DaemonSet runs privileged with host networking and host filesystem access, a malicious image can obtain node and cluster-admin access when the host already has permission to deploy it. This issue is fixed in version 53.4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Kubeshark is an eBPF-powered network observability tool for Kubernetes. From 53.1.0 until 53.4.0, the start_kubeshark MCP tool in cmd/mcpRunner.go uses callStartKubeshark to append caller-controlled pod_regex as a bare positional argument to kubeshark tap without a -- end-of-options separator, allowing a value beginning with --set to be parsed as a Helm value override. An attacker who influences tool arguments against kubeshark mcp --allow-destructive can redirect the privileged worker, Hub, and front images through tap.docker.registry and tap.docker.tag to an attacker-controlled registry. Because the deployed worker DaemonSet runs privileged with host networking and host filesystem access, a malicious image can obtain node and cluster-admin access when the host already has permission to deploy it. This issue is fixed in version 53.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-129236</guid>
    </item>
    <item>
      <title>GHSA-8vf2-hxg5-crqh — Kubeshark: MCP `start_kubeshark` argument injection via `pod_regex` → image redirect → cluster takeover</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8vf2-hxg5-crqh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/kubeshark/kubeshark&lt;/p&gt;
&lt;p&gt;**Ecosystem / package:** Go — `github.com/kubeshark/kubeshark` (the `kubeshark`
CLI, `kubeshark mcp` subcommand)
**Affected component:** `cmd/mcpRunner.go`, MCP tool `start_kubeshark`
**Affected versions:** `&amp;gt;= v53.1.0`, `&amp;lt; v53.4.0` (the flaw shipped with the MCP
command&amp;#39;s first release; v53.3.0 was the last affected release)
**Patched version:** `v53.4.0`
**Credit:** novice-22 (Urim), via private coordinated disclosure.&lt;/p&gt;
&lt;p&gt;## Summary
The `start_kubeshark` MCP tool builds a `kubeshark tap` command by appending the
caller-supplied `pod_regex` as a bare positional argument, with no `--`
end-of-options separator. Because `tap` is a cobra command, a `pod_regex` that
begins with `-`/`--set=` is parsed as a **flag**, not as the pod regex. An
attacker who can influence the tool arguments (e.g. indirect prompt injection
against an agent driving `kubeshark mcp --allow-destructive`) can inject
arbitrary `--set` Helm value overrides — notably `tap.docker.registry` /
`tap.docker.tag` — redirecting the deployed worker/hub/front images to an
attacker-controlled registry. The worker DaemonSet runs privileged with
`hostNetwork` and the host filesystem mounted, so an attacker image yields node
and cluster-admin compromise.&lt;/p&gt;
&lt;p&gt;## Introduced in
Commit `0bbbb473` — &amp;#34;[1] Add MCP (Model Context Protocol) server command
(#1832)&amp;#34;, 2026-02-06 — first released in **v53.1.0** (`v53.1.0~23`). The
`pod_regex` argument has been appended as a bare positional since the tool&amp;#39;s
introduction; there is no regressi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/kubeshark/kubeshark&lt;/p&gt;
&lt;p&gt;**Ecosystem / package:** Go — `github.com/kubeshark/kubeshark` (the `kubeshark`
CLI, `kubeshark mcp` subcommand)
**Affected component:** `cmd/mcpRunner.go`, MCP tool `start_kubeshark`
**Affected versions:** `&amp;gt;= v53.1.0`, `&amp;lt; v53.4.0` (the flaw shipped with the MCP
command&amp;#39;s first release; v53.3.0 was the last affected release)
**Patched version:** `v53.4.0`
**Credit:** novice-22 (Urim), via private coordinated disclosure.&lt;/p&gt;
&lt;p&gt;## Summary
The `start_kubeshark` MCP tool builds a `kubeshark tap` command by appending the
caller-supplied `pod_regex` as a bare positional argument, with no `--`
end-of-options separator. Because `tap` is a cobra command, a `pod_regex` that
begins with `-`/`--set=` is parsed as a **flag**, not as the pod regex. An
attacker who can influence the tool arguments (e.g. indirect prompt injection
against an agent driving `kubeshark mcp --allow-destructive`) can inject
arbitrary `--set` Helm value overrides — notably `tap.docker.registry` /
`tap.docker.tag` — redirecting the deployed worker/hub/front images to an
attacker-controlled registry. The worker DaemonSet runs privileged with
`hostNetwork` and the host filesystem mounted, so an attacker image yields node
and cluster-admin compromise.&lt;/p&gt;
&lt;p&gt;## Introduced in
Commit `0bbbb473` — &amp;#34;[1] Add MCP (Model Context Protocol) server command
(#1832)&amp;#34;, 2026-02-06 — first released in **v53.1.0** (`v53.1.0~23`). The
`pod_regex` argument has been appended as a bare positional since the tool&amp;#39;s
introduction; there is no regressi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8vf2-hxg5-crqh</guid>
    </item>
  </channel>
</rss>
