<?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, 03 Oct 2026 20:54:30 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-213012</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-213012</link>
      <description>EUVD-2026-213012</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-213012</guid>
    </item>
    <item>
      <title>fkie_cve-2025-24884</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-24884</link>
      <description>&lt;p&gt;kube-audit-rest is a simple logger of mutation/creation requests to the k8s api. If the &amp;#34;full-elastic-stack&amp;#34; example vector configuration was used for a real cluster, the previous values of kubernetes secrets would have been disclosed in the audit messages. This vulnerability is fixed in 1.0.16.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kube-audit-rest is a simple logger of mutation/creation requests to the k8s api. If the &amp;#34;full-elastic-stack&amp;#34; example vector configuration was used for a real cluster, the previous values of kubernetes secrets would have been disclosed in the audit messages. This vulnerability is fixed in 1.0.16.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-24884</guid>
    </item>
    <item>
      <title>GHSA-hcr5-wv4p-h2g2 — kube-audit-rest's example logging configuration could disclose secret values in the audit log</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hcr5-wv4p-h2g2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/RichardoC/kube-audit-rest&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_
If the &amp;#34;full-elastic-stack&amp;#34; example vector configuration was used for a real cluster, the previous values of kubernetes secrets would have been disclosed in the audit messages.&lt;/p&gt;
&lt;p&gt;### Patches
_Has the problem been patched? What versions should users upgrade to?_
The example has been updated to fix this in commit 9df8886b4819409f566233adc7c3b7a43a4096ba&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Replace 
```yaml&lt;/p&gt;
&lt;p&gt;if .request.requestKind.kind == &amp;#34;Secret&amp;#34; {
            del(.request.object.data)
            .request.object.data.redacted = &amp;#34;REDACTED&amp;#34;
            del(.request.oldObject.data)
            .request.oldObject.data.redacted = &amp;#34;REDACTED&amp;#34;
          }
```
In the vector &amp;#34;audit-files-json-parser-and-redaction&amp;#34; step
with
```yaml&lt;/p&gt;
&lt;p&gt;if .request.requestKind.kind == &amp;#34;Secret&amp;#34; {
            # Redact the secret data
            del(.request.object.data)
            .request.object.data.redacted = &amp;#34;REDACTED&amp;#34;
            del(.request.oldObject.data)
            .request.oldObject.data.redacted = &amp;#34;REDACTED&amp;#34;
            # Remove the previously set secret data - Not bothering to parse it as this annotation shouldn&amp;#39;t ever be needed
            del(.request.object.metadata.annotations.[&amp;#34;kubectl.kubernetes.io/last-applied-configuration&amp;#34;])
            del(.request.oldObject.metadata.annotations.[&amp;#34;kubectl.kubernetes.io/last-applied-configuration&amp;#34;])…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/RichardoC/kube-audit-rest&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_
If the &amp;#34;full-elastic-stack&amp;#34; example vector configuration was used for a real cluster, the previous values of kubernetes secrets would have been disclosed in the audit messages.&lt;/p&gt;
&lt;p&gt;### Patches
_Has the problem been patched? What versions should users upgrade to?_
The example has been updated to fix this in commit 9df8886b4819409f566233adc7c3b7a43a4096ba&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Replace 
```yaml&lt;/p&gt;
&lt;p&gt;if .request.requestKind.kind == &amp;#34;Secret&amp;#34; {
            del(.request.object.data)
            .request.object.data.redacted = &amp;#34;REDACTED&amp;#34;
            del(.request.oldObject.data)
            .request.oldObject.data.redacted = &amp;#34;REDACTED&amp;#34;
          }
```
In the vector &amp;#34;audit-files-json-parser-and-redaction&amp;#34; step
with
```yaml&lt;/p&gt;
&lt;p&gt;if .request.requestKind.kind == &amp;#34;Secret&amp;#34; {
            # Redact the secret data
            del(.request.object.data)
            .request.object.data.redacted = &amp;#34;REDACTED&amp;#34;
            del(.request.oldObject.data)
            .request.oldObject.data.redacted = &amp;#34;REDACTED&amp;#34;
            # Remove the previously set secret data - Not bothering to parse it as this annotation shouldn&amp;#39;t ever be needed
            del(.request.object.metadata.annotations.[&amp;#34;kubectl.kubernetes.io/last-applied-configuration&amp;#34;])
            del(.request.oldObject.metadata.annotations.[&amp;#34;kubectl.kubernetes.io/last-applied-configuration&amp;#34;])…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hcr5-wv4p-h2g2</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:14732-1 — govulncheck-vulndb-0.0.20250204T220613-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:14732-1</link>
      <description>&lt;p&gt;govulncheck-vulndb-0.0.20250204T220613-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;govulncheck-vulndb-0.0.20250204T220613-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:14732-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:0429-1 — Security update for govulncheck-vulndb</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0429-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:0429-1</guid>
    </item>
  </channel>
</rss>
