<?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>Thu, 08 Oct 2026 12:37:13 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-161079</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-161079</link>
      <description>EUVD-2026-161079</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-161079</guid>
    </item>
    <item>
      <title>fkie_cve-2024-36127</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-36127</link>
      <description>&lt;p&gt;apko is an apk-based OCI image builder. apko exposures HTTP basic auth credentials from repository and keyring URLs in log output. This vulnerability is fixed in v0.14.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;apko is an apk-based OCI image builder. apko exposures HTTP basic auth credentials from repository and keyring URLs in log output. This vulnerability is fixed in v0.14.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-36127</guid>
    </item>
    <item>
      <title>GHSA-v6mg-7f7p-qmqp — apko Exposure of HTTP basic auth credentials in log output</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v6mg-7f7p-qmqp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: chainguard.dev/apko&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Exposure of HTTP basic auth credentials from repository and keyring URLs in log output&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;There was a handful of instances where the `apko` tool was outputting error messages and log entries where HTTP basic authentication credentials were exposed for one of two reasons:&lt;/p&gt;
&lt;p&gt;1. The`%s` verb was used to format a `url.URL` as a string, which includes un-redacted HTTP basic authentication credentials if they are included in the URL.
2. A string URL value (such as from the configuration YAML file supplied used in an apko execution) was never parsed as a URL, so there was no chance of redacting credentials in the logical flow.&lt;/p&gt;
&lt;p&gt;apko, as well as its companion library `go-apk`, have been updated to ensure URLs are parsed and redacted before being output as string values.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Create a config file like this `apko.yaml`:&lt;/p&gt;
&lt;p&gt;```yaml
contents:
  keyring:
    - https://packages.wolfi.dev/os/wolfi-signing.rsa.pub
  repositories:
    - https://me%40example.com:supersecretpassword@localhost:8080/os
  packages:
    - wolfi-base&lt;/p&gt;
&lt;p&gt;cmd: /bin/sh -l&lt;/p&gt;
&lt;p&gt;archs:
- x86_64
- aarch64
```&lt;/p&gt;
&lt;p&gt;Then run:&lt;/p&gt;
&lt;p&gt;```shell
apko build apko.yaml latest foo.tar --log-level debug
```&lt;/p&gt;
&lt;p&gt;Observe instances of the password being shown verbatim in the log output, such as:&lt;/p&gt;
&lt;p&gt;```text
...
DEBU image configuration:
contents:
    repositories:
        - https://me%40example.com:supersecretpassword@localhost:8080/os
    keyring:
        - https://packages.wolfi.dev/os/wolfi-signing.rsa.pub
    packages:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: chainguard.dev/apko&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Exposure of HTTP basic auth credentials from repository and keyring URLs in log output&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;There was a handful of instances where the `apko` tool was outputting error messages and log entries where HTTP basic authentication credentials were exposed for one of two reasons:&lt;/p&gt;
&lt;p&gt;1. The`%s` verb was used to format a `url.URL` as a string, which includes un-redacted HTTP basic authentication credentials if they are included in the URL.
2. A string URL value (such as from the configuration YAML file supplied used in an apko execution) was never parsed as a URL, so there was no chance of redacting credentials in the logical flow.&lt;/p&gt;
&lt;p&gt;apko, as well as its companion library `go-apk`, have been updated to ensure URLs are parsed and redacted before being output as string values.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Create a config file like this `apko.yaml`:&lt;/p&gt;
&lt;p&gt;```yaml
contents:
  keyring:
    - https://packages.wolfi.dev/os/wolfi-signing.rsa.pub
  repositories:
    - https://me%40example.com:supersecretpassword@localhost:8080/os
  packages:
    - wolfi-base&lt;/p&gt;
&lt;p&gt;cmd: /bin/sh -l&lt;/p&gt;
&lt;p&gt;archs:
- x86_64
- aarch64
```&lt;/p&gt;
&lt;p&gt;Then run:&lt;/p&gt;
&lt;p&gt;```shell
apko build apko.yaml latest foo.tar --log-level debug
```&lt;/p&gt;
&lt;p&gt;Observe instances of the password being shown verbatim in the log output, such as:&lt;/p&gt;
&lt;p&gt;```text
...
DEBU image configuration:
contents:
    repositories:
        - https://me%40example.com:supersecretpassword@localhost:8080/os
    keyring:
        - https://packages.wolfi.dev/os/wolfi-signing.rsa.pub
    packages:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v6mg-7f7p-qmqp</guid>
    </item>
  </channel>
</rss>
