<?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>Fri, 02 Oct 2026 16:56:54 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-215187</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-215187</link>
      <description>EUVD-2026-215187</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-215187</guid>
    </item>
    <item>
      <title>fkie_cve-2025-24355</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-24355</link>
      <description>&lt;p&gt;Updatecli is a tool used to apply file update strategies. Prior to version 0.93.0, private maven repository credentials may be leaked in application logs in case of unsuccessful retrieval operation. During the execution of an updatecli pipeline which contains a `maven` source configured with basic auth credentials, the credentials are being leaked in the application execution logs in case of failure. Credentials are properly sanitized when the operation is successful but not when for whatever reason there is a failure in the maven repository, e.g. wrong coordinates provided, not existing artifact or version. Version 0.93.0 contains a patch for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Updatecli is a tool used to apply file update strategies. Prior to version 0.93.0, private maven repository credentials may be leaked in application logs in case of unsuccessful retrieval operation. During the execution of an updatecli pipeline which contains a `maven` source configured with basic auth credentials, the credentials are being leaked in the application execution logs in case of failure. Credentials are properly sanitized when the operation is successful but not when for whatever reason there is a failure in the maven repository, e.g. wrong coordinates provided, not existing artifact or version. Version 0.93.0 contains a patch for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-24355</guid>
    </item>
    <item>
      <title>GHSA-v34r-vj4r-38j6 — Updatecli exposes Maven credentials in console output</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v34r-vj4r-38j6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/updatecli/updatecli&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Private maven repository credentials leaked in application logs in case of unsuccessful retrieval operation.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;During the execution of an updatecli pipeline which contains a `maven` source configured with basic auth credentials, the credentials are being leaked in the application execution logs in case of failure.&lt;/p&gt;
&lt;p&gt;Credentials are properly sanitized when the operation is successful but not when for whatever reason there is a failure in the maven repository .e.g. wrong coordinates provided, not existing artifact or version.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;The [documentation](https://www.updatecli.io/docs/plugins/resource/maven/) currently state to provide user credentials as basic auth inside the `repository` field. e.g.&lt;/p&gt;
&lt;p&gt;```
sources:
  default:
    kind: maven
    spec:
      repository: &amp;#34;{{ requiredEnv &amp;#34;MAVEN_USERNAME&amp;#34; }}:{{ requiredEnv &amp;#34;MAVEN_PASS&amp;#34; }}@repo.example.org/releases&amp;#34;
      groupid: &amp;#34;org.example.company&amp;#34;
      artifactid: &amp;#34;my-artifact&amp;#34;
      versionFilter:
        kind: regex
        pattern: &amp;#34;^23(\.[0-9]+){1,2}$&amp;#34;
```&lt;/p&gt;
&lt;p&gt;Logs are sanitized properly in case of a successful operation:&lt;/p&gt;
&lt;p&gt;```
source: source#default
-----------------------------------------------------------
Searching for version matching pattern &amp;#34;^23(\\.[0-9]+){1,2}$&amp;#34;
✔ Latest version is 23.4.0 on the Maven repository at https://repo.example.org/releases/org/example/company/my-artifact/maven-metadata.xml
```&lt;/p&gt;
&lt;p&gt;but leaks credentials in case the GAV coordinates are wrong (misspelled package name or miss…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/updatecli/updatecli&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Private maven repository credentials leaked in application logs in case of unsuccessful retrieval operation.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;During the execution of an updatecli pipeline which contains a `maven` source configured with basic auth credentials, the credentials are being leaked in the application execution logs in case of failure.&lt;/p&gt;
&lt;p&gt;Credentials are properly sanitized when the operation is successful but not when for whatever reason there is a failure in the maven repository .e.g. wrong coordinates provided, not existing artifact or version.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;The [documentation](https://www.updatecli.io/docs/plugins/resource/maven/) currently state to provide user credentials as basic auth inside the `repository` field. e.g.&lt;/p&gt;
&lt;p&gt;```
sources:
  default:
    kind: maven
    spec:
      repository: &amp;#34;{{ requiredEnv &amp;#34;MAVEN_USERNAME&amp;#34; }}:{{ requiredEnv &amp;#34;MAVEN_PASS&amp;#34; }}@repo.example.org/releases&amp;#34;
      groupid: &amp;#34;org.example.company&amp;#34;
      artifactid: &amp;#34;my-artifact&amp;#34;
      versionFilter:
        kind: regex
        pattern: &amp;#34;^23(\.[0-9]+){1,2}$&amp;#34;
```&lt;/p&gt;
&lt;p&gt;Logs are sanitized properly in case of a successful operation:&lt;/p&gt;
&lt;p&gt;```
source: source#default
-----------------------------------------------------------
Searching for version matching pattern &amp;#34;^23(\\.[0-9]+){1,2}$&amp;#34;
✔ Latest version is 23.4.0 on the Maven repository at https://repo.example.org/releases/org/example/company/my-artifact/maven-metadata.xml
```&lt;/p&gt;
&lt;p&gt;but leaks credentials in case the GAV coordinates are wrong (misspelled package name or miss…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v34r-vj4r-38j6</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:14710-1 — govulncheck-vulndb-0.0.20250128T150132-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:14710-1</link>
      <description>&lt;p&gt;govulncheck-vulndb-0.0.20250128T150132-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;govulncheck-vulndb-0.0.20250128T150132-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:14710-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:0297-1 — Security update for govulncheck-vulndb</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0297-1</link>
      <description>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:0297-1</guid>
    </item>
  </channel>
</rss>
