<?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>Tue, 06 Oct 2026 04:26:39 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-326505</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-326505</link>
      <description>EUVD-2026-326505</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-326505</guid>
    </item>
    <item>
      <title>fkie_cve-2026-49822</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-49822</link>
      <description>&lt;p&gt;Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.24.0, a low-privilege developer who could create a KubernetesWatchTrigger (KWT) in their own namespace was able to establish a persistent surveillance channel over any other namespace. This issue has been patched in version 1.24.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.24.0, a low-privilege developer who could create a KubernetesWatchTrigger (KWT) in their own namespace was able to establish a persistent surveillance channel over any other namespace. This issue has been patched in version 1.24.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-49822</guid>
    </item>
    <item>
      <title>GHSA-gc3j-79f2-7vvw — Fission: Cross-namespace event leakage via KubernetesWatchTrigger allows persistent tenant surveillance</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gc3j-79f2-7vvw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/fission/fission&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A low-privilege developer who could create a `KubernetesWatchTrigger` (KWT) in their own namespace was able to establish a persistent surveillance channel over any other namespace.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Two independent flaws compounded:&lt;/p&gt;
&lt;p&gt;1. `pkg/kubewatcher/kubewatcher.go::createKubernetesWatch` used `w.Spec.Namespace` (user-controlled) directly as the Watch target without checking it against `w.Namespace` (the KWT&amp;#39;s own namespace). `kubewatcher` established the Watch
using its cluster-scoped service account and serialized every Pod/Service/Job change event as full JSON over HTTP POST to the attacker&amp;#39;s function.
2. The validating webhook (`pkg/webhook/kuberneteswatchtrigger.go`) registered `verbs=create` only, so `update`/`patch` requests bypassed validation entirely.&lt;/p&gt;
&lt;p&gt;A separate leak: an empty `spec.namespace` resolved to **all namespaces** via the controller&amp;#39;s default, letting an attacker omit the field to surveil the entire cluster.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A tenant with `kuberneteswatchtriggers.fission.io/create` could continuously receive full event payloads for Pods, Services, and Jobs in any namespace — a persistent cross-tenant surveillance channel requiring no additional privileges.&lt;/p&gt;
&lt;p&gt;### Fix&lt;/p&gt;
&lt;p&gt;Fixed in [#3379](https://github.com/fission/fission/pull/3379) and released in [v1.24.0](https://github.com/fission/fission/releases/tag/v1.24.0).&lt;/p&gt;
&lt;p&gt;- The validating webhook marker is extended to `verbs=create;update`.
- `Validate` rejects `KubernetesWatchTrigger.spec.namespace != meta…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/fission/fission&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A low-privilege developer who could create a `KubernetesWatchTrigger` (KWT) in their own namespace was able to establish a persistent surveillance channel over any other namespace.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Two independent flaws compounded:&lt;/p&gt;
&lt;p&gt;1. `pkg/kubewatcher/kubewatcher.go::createKubernetesWatch` used `w.Spec.Namespace` (user-controlled) directly as the Watch target without checking it against `w.Namespace` (the KWT&amp;#39;s own namespace). `kubewatcher` established the Watch
using its cluster-scoped service account and serialized every Pod/Service/Job change event as full JSON over HTTP POST to the attacker&amp;#39;s function.
2. The validating webhook (`pkg/webhook/kuberneteswatchtrigger.go`) registered `verbs=create` only, so `update`/`patch` requests bypassed validation entirely.&lt;/p&gt;
&lt;p&gt;A separate leak: an empty `spec.namespace` resolved to **all namespaces** via the controller&amp;#39;s default, letting an attacker omit the field to surveil the entire cluster.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A tenant with `kuberneteswatchtriggers.fission.io/create` could continuously receive full event payloads for Pods, Services, and Jobs in any namespace — a persistent cross-tenant surveillance channel requiring no additional privileges.&lt;/p&gt;
&lt;p&gt;### Fix&lt;/p&gt;
&lt;p&gt;Fixed in [#3379](https://github.com/fission/fission/pull/3379) and released in [v1.24.0](https://github.com/fission/fission/releases/tag/v1.24.0).&lt;/p&gt;
&lt;p&gt;- The validating webhook marker is extended to `verbs=create;update`.
- `Validate` rejects `KubernetesWatchTrigger.spec.namespace != meta…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gc3j-79f2-7vvw</guid>
    </item>
  </channel>
</rss>
