<?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>Sun, 18 Oct 2026 04:10:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-28206</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-28206</link>
      <description>EUVD-2026-28206</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-28206</guid>
    </item>
    <item>
      <title>fkie_cve-2021-32770</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-32770</link>
      <description>&lt;p&gt;Gatsby is a framework for building websites. The gatsby-source-wordpress plugin prior to versions 4.0.8 and 5.9.2 leaks .htaccess HTTP Basic Authentication variables into the app.js bundle during build-time. Users who are not initializing basic authentication credentials in the gatsby-config.js are not affected. A patch has been introduced in gatsby-source-wordpress@4.0.8 and gatsby-source-wordpress@5.9.2 which mitigates the issue by filtering all variables specified in the `auth: { }` section. Users that depend on this functionality are advised to upgrade to the latest release of gatsby-source-wordpress, run `gatsby clean` followed by a `gatsby build`. One may manually edit the app.js file post-build as a workaround.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Gatsby is a framework for building websites. The gatsby-source-wordpress plugin prior to versions 4.0.8 and 5.9.2 leaks .htaccess HTTP Basic Authentication variables into the app.js bundle during build-time. Users who are not initializing basic authentication credentials in the gatsby-config.js are not affected. A patch has been introduced in gatsby-source-wordpress@4.0.8 and gatsby-source-wordpress@5.9.2 which mitigates the issue by filtering all variables specified in the `auth: { }` section. Users that depend on this functionality are advised to upgrade to the latest release of gatsby-source-wordpress, run `gatsby clean` followed by a `gatsby build`. One may manually edit the app.js file post-build as a workaround.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-32770</guid>
    </item>
    <item>
      <title>GHSA-rqjw-p5vr-c695 — Basic-auth app bundle credential exposure in gatsby-source-wordpress</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rqjw-p5vr-c695</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: gatsby-source-wordpress&lt;/p&gt;
&lt;p&gt;### Impact
The gatsby-source-wordpress plugin prior to versions 4.0.8 and 5.9.2 leaks .htaccess HTTP Basic Authentication variables into the app.js bundle during build-time.  Users who are not initializing basic authentication credentials in the gatsby-config.js are not affected.&lt;/p&gt;
&lt;p&gt;Example affected gatsby-config.js:
```
      resolve: &amp;#39;gatsby-source-wordpress&amp;#39;,
        auth: {
          htaccess: {
            username: leaked_username
            password: leaked_password,
          },
        },
```&lt;/p&gt;
&lt;p&gt;### Patches
A patch has been introduced in gatsby-source-wordpress@4.0.8 and gatsby-source-wordpress@5.9.2 which mitigates the issue by filtering all variables specified in the `auth: { }` section.  Users that depend on this functionality are advised to upgrade to the latest release of gatsby-source-wordpress, run `gatsby clean` followed by a `gatsby build`.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no known workaround at this time, other than manually editing the app.js file post-build.&lt;/p&gt;
&lt;p&gt;### For more information
Email us at [security@gatsbyjs.com](mailto:security@gatsbyjs.com)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: gatsby-source-wordpress&lt;/p&gt;
&lt;p&gt;### Impact
The gatsby-source-wordpress plugin prior to versions 4.0.8 and 5.9.2 leaks .htaccess HTTP Basic Authentication variables into the app.js bundle during build-time.  Users who are not initializing basic authentication credentials in the gatsby-config.js are not affected.&lt;/p&gt;
&lt;p&gt;Example affected gatsby-config.js:
```
      resolve: &amp;#39;gatsby-source-wordpress&amp;#39;,
        auth: {
          htaccess: {
            username: leaked_username
            password: leaked_password,
          },
        },
```&lt;/p&gt;
&lt;p&gt;### Patches
A patch has been introduced in gatsby-source-wordpress@4.0.8 and gatsby-source-wordpress@5.9.2 which mitigates the issue by filtering all variables specified in the `auth: { }` section.  Users that depend on this functionality are advised to upgrade to the latest release of gatsby-source-wordpress, run `gatsby clean` followed by a `gatsby build`.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no known workaround at this time, other than manually editing the app.js file post-build.&lt;/p&gt;
&lt;p&gt;### For more information
Email us at [security@gatsbyjs.com](mailto:security@gatsbyjs.com)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rqjw-p5vr-c695</guid>
    </item>
    <item>
      <title>gsd-2021-32770</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-32770</link>
      <description>gsd-2021-32770</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-32770</guid>
    </item>
  </channel>
</rss>
