<?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://db.gcve.eu</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, 10 Nov 2026 04:20:26 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-88986</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-88986</link>
      <description>&lt;p&gt;Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.15.0, the frontend routes /pipeline/k8s/pod and /pipeline/k8s/pod/events use frontend/server/k8s-helper.ts to include untrusted podname and podnamespace query values and backend error details in HTML-capable error responses. An unauthenticated attacker can craft a link that executes JavaScript in the frontend origin when a user who satisfies the deployment&amp;#39;s authentication and route-access requirements follows it and reaches an affected response. Cookie disclosure depends on cookie attributes, and server-side code execution or availability impact is not established. This issue is fixed in version 2.15.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.15.0, the frontend routes /pipeline/k8s/pod and /pipeline/k8s/pod/events use frontend/server/k8s-helper.ts to include untrusted podname and podnamespace query values and backend error details in HTML-capable error responses. An unauthenticated attacker can craft a link that executes JavaScript in the frontend origin when a user who satisfies the deployment&amp;#39;s authentication and route-access requirements follows it and reaches an affected response. Cookie disclosure depends on cookie attributes, and server-side code execution or availability impact is not established. This issue is fixed in version 2.15.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-88986</guid>
    </item>
    <item>
      <title>GHSA-g3qx-frcg-j979 — Kubeflow Pipelines: Reflected XSS in the frontend pod information and events error responses</title>
      <link>https://db.gcve.eu/vuln/ghsa-g3qx-frcg-j979</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/kubeflow/pipelines&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The Kubeflow Pipelines frontend reflected untrusted pod names and namespaces into HTML error responses from the pod-information and pod-events routes. An attacker could craft a link that causes JavaScript to execute in the frontend&amp;#39;s origin when a user follows it and reaches an affected error response.&lt;/p&gt;
&lt;p&gt;Affected routes include `/pipeline/k8s/pod` and `/pipeline/k8s/pod/events` (the deployment&amp;#39;s configured base path may differ).&lt;/p&gt;
&lt;p&gt;## Impact and prerequisites&lt;/p&gt;
&lt;p&gt;Successful exploitation requires a victim to open an attacker-supplied link and reach the vulnerable response. JavaScript execution may expose information accessible to the victim&amp;#39;s browser or perform actions in the application&amp;#39;s origin.&lt;/p&gt;
&lt;p&gt;The attacker does not need an account merely to construct and deliver the link. The victim must satisfy the deployment&amp;#39;s authentication and route-access requirements. Cookie theft depends on cookie attributes and deployment protections; it is not guaranteed. The submitted evidence does not establish an availability impact or server-side code execution.&lt;/p&gt;
&lt;p&gt;## Technical details&lt;/p&gt;
&lt;p&gt;The pod handlers pass `podname` and `podnamespace` query values to `getPod` and `listPodEvents` in `frontend/server/k8s-helper.ts`. Before remediation, failure messages incorporated those values, along with backend error details, and were returned as HTML-capable string responses.&lt;/p&gt;
&lt;p&gt;Kubernetes rejecting an invalid resource name did not prevent the issue: the rejected name could still be included in the fro…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/kubeflow/pipelines&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The Kubeflow Pipelines frontend reflected untrusted pod names and namespaces into HTML error responses from the pod-information and pod-events routes. An attacker could craft a link that causes JavaScript to execute in the frontend&amp;#39;s origin when a user follows it and reaches an affected error response.&lt;/p&gt;
&lt;p&gt;Affected routes include `/pipeline/k8s/pod` and `/pipeline/k8s/pod/events` (the deployment&amp;#39;s configured base path may differ).&lt;/p&gt;
&lt;p&gt;## Impact and prerequisites&lt;/p&gt;
&lt;p&gt;Successful exploitation requires a victim to open an attacker-supplied link and reach the vulnerable response. JavaScript execution may expose information accessible to the victim&amp;#39;s browser or perform actions in the application&amp;#39;s origin.&lt;/p&gt;
&lt;p&gt;The attacker does not need an account merely to construct and deliver the link. The victim must satisfy the deployment&amp;#39;s authentication and route-access requirements. Cookie theft depends on cookie attributes and deployment protections; it is not guaranteed. The submitted evidence does not establish an availability impact or server-side code execution.&lt;/p&gt;
&lt;p&gt;## Technical details&lt;/p&gt;
&lt;p&gt;The pod handlers pass `podname` and `podnamespace` query values to `getPod` and `listPodEvents` in `frontend/server/k8s-helper.ts`. Before remediation, failure messages incorporated those values, along with backend error details, and were returned as HTML-capable string responses.&lt;/p&gt;
&lt;p&gt;Kubernetes rejecting an invalid resource name did not prevent the issue: the rejected name could still be included in the fro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-g3qx-frcg-j979</guid>
    </item>
  </channel>
</rss>
