<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T19:52:21.774442+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-215187</id>
    <title>EUVD-2026-215187</title>
    <updated>2026-10-02T19:52:21.843944+00:00</updated>
    <content>EUVD-2026-215187</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-215187"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-24355</id>
    <title>fkie_cve-2025-24355</title>
    <updated>2026-10-02T19:52:21.843989+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-24355"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-v34r-vj4r-38j6</id>
    <title>GHSA-v34r-vj4r-38j6 — Updatecli exposes Maven credentials in console output</title>
    <updated>2026-10-02T19:52:21.844039+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/updatecli/updatecli</p>
<p>### Summary</p>
<p>Private maven repository credentials leaked in application logs in case of unsuccessful retrieval operation.</p>
<p>### Details</p>
<p>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.</p>
<p>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.</p>
<p>### PoC</p>
<p>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.</p>
<p>```
sources:
  default:
    kind: maven
    spec:
      repository: "{{ requiredEnv "MAVEN_USERNAME" }}:{{ requiredEnv "MAVEN_PASS" }}@repo.example.org/releases"
      groupid: "org.example.company"
      artifactid: "my-artifact"
      versionFilter:
        kind: regex
        pattern: "^23(\.[0-9]+){1,2}$"
```</p>
<p>Logs are sanitized properly in case of a successful operation:</p>
<p>```
source: source#default
-----------------------------------------------------------
Searching for version matching pattern "^23(\\.[0-9]+){1,2}$"
✔ Latest version is 23.4.0 on the Maven repository at https://repo.example.org/releases/org/example/company/my-artifact/maven-metadata.xml
```</p>
<p>but leaks credentials in case the GAV coordinates are wrong (misspelled package name or miss…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-v34r-vj4r-38j6"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2025:14710-1</id>
    <title>openSUSE-SU-2025:14710-1 — govulncheck-vulndb-0.0.20250128T150132-1.1 on GA media</title>
    <updated>2026-10-02T19:52:21.844122+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>govulncheck-vulndb-0.0.20250128T150132-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2025:14710-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2025:0297-1</id>
    <title>SUSE-SU-2025:0297-1 — Security update for govulncheck-vulndb</title>
    <updated>2026-10-02T19:52:21.844160+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for govulncheck-vulndb</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2025:0297-1"/>
  </entry>
</feed>
