<?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 17:25:53 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-326514</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-326514</link>
      <description>EUVD-2026-326514</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-326514</guid>
    </item>
    <item>
      <title>fkie_cve-2026-50569</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-50569</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.25.0, HTTPTriggerSpec.Validate() validated Methods, FunctionReference, Host, IngressConfig, and CorsConfig, but silently skipped RelativeURL and Prefix. Those two fields were validated at the CLI level only (pkg/fission-cli/cmd/httptrigger/create.go:83). The post-CRD-modernization webhook for HTTPTrigger was retired in favor of API-server CEL — and CEL had no rules on those fields either — so an HTTPTrigger created via kubectl apply or a direct Kubernetes REST API call bypassed every URL-level check. This issue has been patched in version 1.25.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.25.0, HTTPTriggerSpec.Validate() validated Methods, FunctionReference, Host, IngressConfig, and CorsConfig, but silently skipped RelativeURL and Prefix. Those two fields were validated at the CLI level only (pkg/fission-cli/cmd/httptrigger/create.go:83). The post-CRD-modernization webhook for HTTPTrigger was retired in favor of API-server CEL — and CEL had no rules on those fields either — so an HTTPTrigger created via kubectl apply or a direct Kubernetes REST API call bypassed every URL-level check. This issue has been patched in version 1.25.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-50569</guid>
    </item>
    <item>
      <title>GHSA-vchh-r53j-8mpw — Fission: HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vchh-r53j-8mpw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/fission/fission&lt;/p&gt;
&lt;p&gt;`HTTPTriggerSpec.Validate()` validated `Methods`, `FunctionReference`, `Host`, `IngressConfig`, and `CorsConfig`, but silently skipped `RelativeURL` and `Prefix`. Those two fields were validated at the CLI level only
(`pkg/fission-cli/cmd/httptrigger/create.go:83`). The post-CRD-modernization webhook for HTTPTrigger was retired in favor of API-server CEL — and CEL had no rules on those fields either — so an HTTPTrigger created via `kubectl apply` or
a direct Kubernetes REST API call bypassed every URL-level check.&lt;/p&gt;
&lt;p&gt;A tenant with HTTPTrigger create permission could therefore create triggers whose `RelativeURL` or `Prefix`:&lt;/p&gt;
&lt;p&gt;- was empty (with both fields unset, the trigger has no URL),
- did not start with `/`,
- was exactly `/` (claiming the entire router root),
- contained `..` traversal segments (e.g. `/api/../admin`),
- collided with router-owned routes: `/router-healthz`, `/readyz`, `/_version`, `/auth/login`,
- collided with the router-internal function prefix `/fission-function/&amp;lt;ns&amp;gt;/&amp;lt;name&amp;gt;`.&lt;/p&gt;
&lt;p&gt;### Affected&lt;/p&gt;
&lt;p&gt;- Project: `github.com/fission/fission`
- Versions: all versions through v1.24.0
- Audited commit: `647c141`
- Component: `pkg/apis/core/v1/validation.go:HTTPTriggerSpec.Validate` (and the missing CEL on `HTTPTriggerSpec`)
- Configuration: default&lt;/p&gt;
&lt;p&gt;Fix section (paste into the Fix / Patches field)&lt;/p&gt;
&lt;p&gt;Fixed in [v1.25.0](https://github.com/fission/fission/releases/tag/v1.25.0) by:&lt;/p&gt;
&lt;p&gt;- [PR #3464](https://github.com/fission/fission/pull/3464) (commit [`0deed6bf`](https://gith…&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;`HTTPTriggerSpec.Validate()` validated `Methods`, `FunctionReference`, `Host`, `IngressConfig`, and `CorsConfig`, but silently skipped `RelativeURL` and `Prefix`. Those two fields were validated at the CLI level only
(`pkg/fission-cli/cmd/httptrigger/create.go:83`). The post-CRD-modernization webhook for HTTPTrigger was retired in favor of API-server CEL — and CEL had no rules on those fields either — so an HTTPTrigger created via `kubectl apply` or
a direct Kubernetes REST API call bypassed every URL-level check.&lt;/p&gt;
&lt;p&gt;A tenant with HTTPTrigger create permission could therefore create triggers whose `RelativeURL` or `Prefix`:&lt;/p&gt;
&lt;p&gt;- was empty (with both fields unset, the trigger has no URL),
- did not start with `/`,
- was exactly `/` (claiming the entire router root),
- contained `..` traversal segments (e.g. `/api/../admin`),
- collided with router-owned routes: `/router-healthz`, `/readyz`, `/_version`, `/auth/login`,
- collided with the router-internal function prefix `/fission-function/&amp;lt;ns&amp;gt;/&amp;lt;name&amp;gt;`.&lt;/p&gt;
&lt;p&gt;### Affected&lt;/p&gt;
&lt;p&gt;- Project: `github.com/fission/fission`
- Versions: all versions through v1.24.0
- Audited commit: `647c141`
- Component: `pkg/apis/core/v1/validation.go:HTTPTriggerSpec.Validate` (and the missing CEL on `HTTPTriggerSpec`)
- Configuration: default&lt;/p&gt;
&lt;p&gt;Fix section (paste into the Fix / Patches field)&lt;/p&gt;
&lt;p&gt;Fixed in [v1.25.0](https://github.com/fission/fission/releases/tag/v1.25.0) by:&lt;/p&gt;
&lt;p&gt;- [PR #3464](https://github.com/fission/fission/pull/3464) (commit [`0deed6bf`](https://gith…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vchh-r53j-8mpw</guid>
    </item>
  </channel>
</rss>
