<?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>Wed, 07 Oct 2026 14:15:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-0913 — Inconsistent handling of O_CREATE|O_EXCL on Unix and Windows in os in syscall</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-0913</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go standard library syscall, Go standard library os&lt;/p&gt;
&lt;p&gt;os.OpenFile(path, os.O_CREATE|O_EXCL) behaved differently on Unix and Windows systems when the target path was a dangling symlink. On Unix systems, OpenFile with O_CREATE and O_EXCL flags never follows symlinks. On Windows, when the target path was a symlink to a nonexistent location, OpenFile would create a file in that location. OpenFile now always returns an error when the O_CREATE and O_EXCL flags are both set and the target path is a symlink.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go standard library syscall, Go standard library os&lt;/p&gt;
&lt;p&gt;os.OpenFile(path, os.O_CREATE|O_EXCL) behaved differently on Unix and Windows systems when the target path was a dangling symlink. On Unix systems, OpenFile with O_CREATE and O_EXCL flags never follows symlinks. On Windows, when the target path was a symlink to a nonexistent location, OpenFile would create a file in that location. OpenFile now always returns an error when the O_CREATE and O_EXCL flags are both set and the target path is a symlink.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-0913</guid>
    </item>
    <item>
      <title>GHSA-c2hv-4pfj-mm2r — Argo Workflow may expose artifact repository credentials</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c2hv-4pfj-mm2r</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/argoproj/argo-workflows/v3&lt;/p&gt;
&lt;p&gt;### Summary
An attacker who has permissions to read logs from pods in a namespace with Argo Workflow can read `workflow-controller` logs and get credentials to the artifact repository.&lt;/p&gt;
&lt;p&gt;### Details
An attacker, by reading the logs of the workflow controller pod, can access the artifact repository, and steal, delete or modify the data that resides there. The `workflow-controller` logs show the credentials in plaintext.&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;1366&amp;#34; alt=&amp;#34;screen&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/5642b2be-edcf-4050-bf47-747d05352698&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;### Impact
An attacker with access to pod logs in the `argo` namespace can extract plaintext credentials from the `workflow-controller` logs and gain access to the artifact repository. This can lead to:
- Data exfiltration – theft of sensitive or proprietary artifacts
- Data tampering – modification of workflows or artifacts
- Data destruction – deletion of stored artifacts, leading to potential loss of critical data or pipeline failure&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/argoproj/argo-workflows/v3&lt;/p&gt;
&lt;p&gt;### Summary
An attacker who has permissions to read logs from pods in a namespace with Argo Workflow can read `workflow-controller` logs and get credentials to the artifact repository.&lt;/p&gt;
&lt;p&gt;### Details
An attacker, by reading the logs of the workflow controller pod, can access the artifact repository, and steal, delete or modify the data that resides there. The `workflow-controller` logs show the credentials in plaintext.&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;1366&amp;#34; alt=&amp;#34;screen&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/5642b2be-edcf-4050-bf47-747d05352698&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;### Impact
An attacker with access to pod logs in the `argo` namespace can extract plaintext credentials from the `workflow-controller` logs and gain access to the artifact repository. This can lead to:
- Data exfiltration – theft of sensitive or proprietary artifacts
- Data tampering – modification of workflows or artifacts
- Data destruction – deletion of stored artifacts, leading to potential loss of critical data or pipeline failure&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c2hv-4pfj-mm2r</guid>
    </item>
  </channel>
</rss>
