<?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>Mon, 12 Oct 2026 19:48:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-213502</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-213502</link>
      <description>EUVD-2026-213502</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-213502</guid>
    </item>
    <item>
      <title>fkie_cve-2023-30618</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-30618</link>
      <description>&lt;p&gt;Kitchen-Terraform provides a set of Test Kitchen plugins which enable the use of Test Kitchen to converge a Terraform configuration and verify the resulting infrastructure systems with InSpec controls. Kitchen-Terraform v7.0.0 introduced a regression which caused all Terraform output values, including sensitive values, to be printed at the `info` logging level during the `kitchen converge` action. Prior to v7.0.0, the output values were printed at the `debug` level to avoid writing sensitive values to the terminal by default. An attacker would need access to the local machine in order to gain access to these logs during an operation. Users are advised to upgrade. There are no known workarounds for this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Kitchen-Terraform provides a set of Test Kitchen plugins which enable the use of Test Kitchen to converge a Terraform configuration and verify the resulting infrastructure systems with InSpec controls. Kitchen-Terraform v7.0.0 introduced a regression which caused all Terraform output values, including sensitive values, to be printed at the `info` logging level during the `kitchen converge` action. Prior to v7.0.0, the output values were printed at the `debug` level to avoid writing sensitive values to the terminal by default. An attacker would need access to the local machine in order to gain access to these logs during an operation. Users are advised to upgrade. There are no known workarounds for this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-30618</guid>
    </item>
    <item>
      <title>GHSA-65g2-x53q-cmf6 — Sensitive Terraform Output Values Printed At Info Logging Level In Kitchen-Terraform</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-65g2-x53q-cmf6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: kitchen-terraform&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Kitchen-Terraform v7.0.0 introduced a regression which caused all Terraform output values, including sensitive values, to be printed at the `info` logging level during the `kitchen converge` action. Prior to v7.0.0, the output values were printed at the `debug` level to avoid writing sensitive values to the terminal by default.&lt;/p&gt;
&lt;p&gt;### Original Report&lt;/p&gt;
&lt;p&gt;@brettcurtis:
&amp;gt; Hopefully, I&amp;#39;m not doing something stupid here, but I&amp;#39;m seeing sensitive outputs printed in the kitchen output. You can check this action for an example: https://github.com/osinfra-io/terraform-google-project/actions/runs/4700065515/jobs/8334277309#step:5:215
&amp;gt;
&amp;gt; It&amp;#39;s not really a sensitive value just used it as an example.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: kitchen-terraform&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Kitchen-Terraform v7.0.0 introduced a regression which caused all Terraform output values, including sensitive values, to be printed at the `info` logging level during the `kitchen converge` action. Prior to v7.0.0, the output values were printed at the `debug` level to avoid writing sensitive values to the terminal by default.&lt;/p&gt;
&lt;p&gt;### Original Report&lt;/p&gt;
&lt;p&gt;@brettcurtis:
&amp;gt; Hopefully, I&amp;#39;m not doing something stupid here, but I&amp;#39;m seeing sensitive outputs printed in the kitchen output. You can check this action for an example: https://github.com/osinfra-io/terraform-google-project/actions/runs/4700065515/jobs/8334277309#step:5:215
&amp;gt;
&amp;gt; It&amp;#39;s not really a sensitive value just used it as an example.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-65g2-x53q-cmf6</guid>
    </item>
    <item>
      <title>gsd-2023-30618</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-30618</link>
      <description>gsd-2023-30618</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-30618</guid>
    </item>
  </channel>
</rss>
