<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T06:24:57.072056+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-326505</id>
    <title>EUVD-2026-326505</title>
    <updated>2026-10-06T06:24:57.134521+00:00</updated>
    <content>EUVD-2026-326505</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-326505"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-49822</id>
    <title>fkie_cve-2026-49822</title>
    <updated>2026-10-06T06:24:57.134580+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-49822"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-gc3j-79f2-7vvw</id>
    <title>GHSA-gc3j-79f2-7vvw — Fission: Cross-namespace event leakage via KubernetesWatchTrigger allows persistent tenant surveillance</title>
    <updated>2026-10-06T06:24:57.134640+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/fission/fission</p>
<p>### Summary</p>
<p>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.</p>
<p>### Details</p>
<p>Two independent flaws compounded:</p>
<p>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'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's function.
2. The validating webhook (`pkg/webhook/kuberneteswatchtrigger.go`) registered `verbs=create` only, so `update`/`patch` requests bypassed validation entirely.</p>
<p>A separate leak: an empty `spec.namespace` resolved to **all namespaces** via the controller's default, letting an attacker omit the field to surveil the entire cluster.</p>
<p>### Impact</p>
<p>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.</p>
<p>### Fix</p>
<p>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).</p>
<p>- The validating webhook marker is extended to `verbs=create;update`.
- `Validate` rejects `KubernetesWatchTrigger.spec.namespace != meta…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-gc3j-79f2-7vvw"/>
  </entry>
</feed>
