<?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 07:09:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-159310</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-159310</link>
      <description>EUVD-2026-159310</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-159310</guid>
    </item>
    <item>
      <title>fkie_cve-2024-36105</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-36105</link>
      <description>&lt;p&gt;dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications. Prior to versions 1.6.15, 1.7.15, and 1.8.1, Binding to `INADDR_ANY (0.0.0.0)` or `IN6ADDR_ANY (::)` exposes an application on all network interfaces, increasing the risk of unauthorized access. As stated in the Python docs, a special form for address is accepted instead of a host address: `&amp;#39;&amp;#39;` represents `INADDR_ANY`, equivalent to `&amp;#34;0.0.0.0&amp;#34;`. On systems with IPv6, &amp;#39;&amp;#39; represents `IN6ADDR_ANY`, which is equivalent to `&amp;#34;::&amp;#34;`. A user who serves docs on an unsecured public network, may unknowingly be hosting an unsecured (http) web site for any remote user/system to access on the same network. The issue has has been mitigated in dbt-core v1.6.15, dbt-core v1.7.15, and dbt-core v1.8.1 by binding to localhost explicitly by default in `dbt docs serve`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications. Prior to versions 1.6.15, 1.7.15, and 1.8.1, Binding to `INADDR_ANY (0.0.0.0)` or `IN6ADDR_ANY (::)` exposes an application on all network interfaces, increasing the risk of unauthorized access. As stated in the Python docs, a special form for address is accepted instead of a host address: `&amp;#39;&amp;#39;` represents `INADDR_ANY`, equivalent to `&amp;#34;0.0.0.0&amp;#34;`. On systems with IPv6, &amp;#39;&amp;#39; represents `IN6ADDR_ANY`, which is equivalent to `&amp;#34;::&amp;#34;`. A user who serves docs on an unsecured public network, may unknowingly be hosting an unsecured (http) web site for any remote user/system to access on the same network. The issue has has been mitigated in dbt-core v1.6.15, dbt-core v1.7.15, and dbt-core v1.8.1 by binding to localhost explicitly by default in `dbt docs serve`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-36105</guid>
    </item>
    <item>
      <title>GHSA-pmrx-695r-4349 — dbt allows Binding to an Unrestricted IP Address via socketsocket</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pmrx-695r-4349</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: dbt-core&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Binding to `INADDR_ANY (0.0.0.0)` or `IN6ADDR_ANY (::)` exposes an application on all network interfaces, increasing the risk of unauthorized access.&lt;/p&gt;
&lt;p&gt;While doing some static analysis and code inspection, I found the following code binding a socket to `INADDR_ANY` by passing `&amp;#34;&amp;#34;` as the address. This effectively binds to any network interface on the local system, not just localhost (127.0.0.1).&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;As stated in the Python docs, a special form for address is accepted instead of a host address: `&amp;#39;&amp;#39;` represents `INADDR_ANY`, equivalent to `&amp;#34;0.0.0.0&amp;#34;`. On systems with IPv6, &amp;#39;&amp;#39; represents `IN6ADDR_ANY`, which is equivalent to `&amp;#34;::&amp;#34;`.&lt;/p&gt;
&lt;p&gt;https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/task/docs/serve.py#L23C38-L23C39&lt;/p&gt;
&lt;p&gt;The text around this code also imply the intention is to host docs only on localhost.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;To recreate, run the docs ServeTask.run() to stand up the HTTP server.  Then run `netstat` to see what addresses this process is bound.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A user who serves docs on an unsecured public network, may unknowingly be hosting an unsecured (http) web site for any remote user/system to access on the same network.&lt;/p&gt;
&lt;p&gt;Further references:
https://docs.python.org/3/library/socket.html#socket-families
https://docs.securesauce.dev/rules/PY030
https://cwe.mitre.org/data/definitions/1327.html&lt;/p&gt;
&lt;p&gt;### Patches
The issue has has been mitigated in [dbt-core v1.6.15](https://github.com/dbt-labs/dbt-core/releases/tag/v1.6.15), [dbt-core v1.7.15](https://gith…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: dbt-core&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Binding to `INADDR_ANY (0.0.0.0)` or `IN6ADDR_ANY (::)` exposes an application on all network interfaces, increasing the risk of unauthorized access.&lt;/p&gt;
&lt;p&gt;While doing some static analysis and code inspection, I found the following code binding a socket to `INADDR_ANY` by passing `&amp;#34;&amp;#34;` as the address. This effectively binds to any network interface on the local system, not just localhost (127.0.0.1).&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;As stated in the Python docs, a special form for address is accepted instead of a host address: `&amp;#39;&amp;#39;` represents `INADDR_ANY`, equivalent to `&amp;#34;0.0.0.0&amp;#34;`. On systems with IPv6, &amp;#39;&amp;#39; represents `IN6ADDR_ANY`, which is equivalent to `&amp;#34;::&amp;#34;`.&lt;/p&gt;
&lt;p&gt;https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/task/docs/serve.py#L23C38-L23C39&lt;/p&gt;
&lt;p&gt;The text around this code also imply the intention is to host docs only on localhost.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;To recreate, run the docs ServeTask.run() to stand up the HTTP server.  Then run `netstat` to see what addresses this process is bound.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A user who serves docs on an unsecured public network, may unknowingly be hosting an unsecured (http) web site for any remote user/system to access on the same network.&lt;/p&gt;
&lt;p&gt;Further references:
https://docs.python.org/3/library/socket.html#socket-families
https://docs.securesauce.dev/rules/PY030
https://cwe.mitre.org/data/definitions/1327.html&lt;/p&gt;
&lt;p&gt;### Patches
The issue has has been mitigated in [dbt-core v1.6.15](https://github.com/dbt-labs/dbt-core/releases/tag/v1.6.15), [dbt-core v1.7.15](https://gith…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pmrx-695r-4349</guid>
    </item>
    <item>
      <title>PYSEC-2026-1292 — dbt allows Binding to an Unrestricted IP Address via socketsocket</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1292</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: dbt-core&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Binding to `INADDR_ANY (0.0.0.0)` or `IN6ADDR_ANY (::)` exposes an application on all network interfaces, increasing the risk of unauthorized access.&lt;/p&gt;
&lt;p&gt;While doing some static analysis and code inspection, I found the following code binding a socket to `INADDR_ANY` by passing `&amp;#34;&amp;#34;` as the address. This effectively binds to any network interface on the local system, not just localhost (127.0.0.1).&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;As stated in the Python docs, a special form for address is accepted instead of a host address: `&amp;#39;&amp;#39;` represents `INADDR_ANY`, equivalent to `&amp;#34;0.0.0.0&amp;#34;`. On systems with IPv6, &amp;#39;&amp;#39; represents `IN6ADDR_ANY`, which is equivalent to `&amp;#34;::&amp;#34;`.&lt;/p&gt;
&lt;p&gt;https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/task/docs/serve.py#L23C38-L23C39&lt;/p&gt;
&lt;p&gt;The text around this code also imply the intention is to host docs only on localhost.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;To recreate, run the docs ServeTask.run() to stand up the HTTP server.  Then run `netstat` to see what addresses this process is bound.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A user who serves docs on an unsecured public network, may unknowingly be hosting an unsecured (http) web site for any remote user/system to access on the same network.&lt;/p&gt;
&lt;p&gt;Further references:
https://docs.python.org/3/library/socket.html#socket-families
https://docs.securesauce.dev/rules/PY030
https://cwe.mitre.org/data/definitions/1327.html&lt;/p&gt;
&lt;p&gt;### Patches
The issue has has been mitigated in [dbt-core v1.6.15](https://github.com/dbt-labs/dbt-core/releases/tag/v1.6.15), [dbt-core v1.7.15](https://gith…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: dbt-core&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Binding to `INADDR_ANY (0.0.0.0)` or `IN6ADDR_ANY (::)` exposes an application on all network interfaces, increasing the risk of unauthorized access.&lt;/p&gt;
&lt;p&gt;While doing some static analysis and code inspection, I found the following code binding a socket to `INADDR_ANY` by passing `&amp;#34;&amp;#34;` as the address. This effectively binds to any network interface on the local system, not just localhost (127.0.0.1).&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;As stated in the Python docs, a special form for address is accepted instead of a host address: `&amp;#39;&amp;#39;` represents `INADDR_ANY`, equivalent to `&amp;#34;0.0.0.0&amp;#34;`. On systems with IPv6, &amp;#39;&amp;#39; represents `IN6ADDR_ANY`, which is equivalent to `&amp;#34;::&amp;#34;`.&lt;/p&gt;
&lt;p&gt;https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/task/docs/serve.py#L23C38-L23C39&lt;/p&gt;
&lt;p&gt;The text around this code also imply the intention is to host docs only on localhost.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;To recreate, run the docs ServeTask.run() to stand up the HTTP server.  Then run `netstat` to see what addresses this process is bound.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A user who serves docs on an unsecured public network, may unknowingly be hosting an unsecured (http) web site for any remote user/system to access on the same network.&lt;/p&gt;
&lt;p&gt;Further references:
https://docs.python.org/3/library/socket.html#socket-families
https://docs.securesauce.dev/rules/PY030
https://cwe.mitre.org/data/definitions/1327.html&lt;/p&gt;
&lt;p&gt;### Patches
The issue has has been mitigated in [dbt-core v1.6.15](https://github.com/dbt-labs/dbt-core/releases/tag/v1.6.15), [dbt-core v1.7.15](https://gith…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1292</guid>
    </item>
  </channel>
</rss>
