<?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, 17 Oct 2026 22:55:44 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-225971</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-225971</link>
      <description>EUVD-2026-225971</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-225971</guid>
    </item>
    <item>
      <title>fkie_cve-2023-24622</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-24622</link>
      <description>&lt;p&gt;isInList in the safeurl-python package before 1.2 for Python has an insufficiently restrictive regular expression for external domains, leading to SSRF.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;isInList in the safeurl-python package before 1.2 for Python has an insufficiently restrictive regular expression for external domains, leading to SSRF.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-24622</guid>
    </item>
    <item>
      <title>GHSA-jgh8-vchw-q3g7 — safeurl-python contains Server-Side Request Forgery</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jgh8-vchw-q3g7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: safeurl-python&lt;/p&gt;
&lt;p&gt;### Description
In SafeURL it is possible to specify a list of domains that should be matched before a request is sent out. The regex used to compare domains did not work as intended.&lt;/p&gt;
&lt;p&gt;### Impact
The regex used was:&lt;/p&gt;
&lt;p&gt;`re.match(&amp;#34;(?i)^%s&amp;#34; % domain, value)`&lt;/p&gt;
&lt;p&gt;This has two problems, first that only the beginning and not the end of the string is anchored. Second, that a dot in the domain matches any character as part of regex syntax.&lt;/p&gt;
&lt;p&gt;Therefore, an allowlist of [&amp;#34;victim.com&amp;#34;] could allow the domain &amp;#34;victimacomattacker.com&amp;#34; to be requested.&lt;/p&gt;
&lt;p&gt;This has lower impact since the usual attacker aim in an SSRF is to request internal resources such as private IP addresses rather than an attacker&amp;#39;s own domain. But, in a case where SafeURL had specifically been used to try to limit requests to a particular allowlist, say for example a PDF renderer, the finding would be more severe.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in https://github.com/IncludeSecurity/safeurl-python/pull/5&lt;/p&gt;
&lt;p&gt;### References
[Server-side request forgery (SSRF)](https://portswigger.net/web-security/ssrf)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: safeurl-python&lt;/p&gt;
&lt;p&gt;### Description
In SafeURL it is possible to specify a list of domains that should be matched before a request is sent out. The regex used to compare domains did not work as intended.&lt;/p&gt;
&lt;p&gt;### Impact
The regex used was:&lt;/p&gt;
&lt;p&gt;`re.match(&amp;#34;(?i)^%s&amp;#34; % domain, value)`&lt;/p&gt;
&lt;p&gt;This has two problems, first that only the beginning and not the end of the string is anchored. Second, that a dot in the domain matches any character as part of regex syntax.&lt;/p&gt;
&lt;p&gt;Therefore, an allowlist of [&amp;#34;victim.com&amp;#34;] could allow the domain &amp;#34;victimacomattacker.com&amp;#34; to be requested.&lt;/p&gt;
&lt;p&gt;This has lower impact since the usual attacker aim in an SSRF is to request internal resources such as private IP addresses rather than an attacker&amp;#39;s own domain. But, in a case where SafeURL had specifically been used to try to limit requests to a particular allowlist, say for example a PDF renderer, the finding would be more severe.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in https://github.com/IncludeSecurity/safeurl-python/pull/5&lt;/p&gt;
&lt;p&gt;### References
[Server-side request forgery (SSRF)](https://portswigger.net/web-security/ssrf)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jgh8-vchw-q3g7</guid>
    </item>
    <item>
      <title>gsd-2023-24622</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-24622</link>
      <description>gsd-2023-24622</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-24622</guid>
    </item>
    <item>
      <title>PYSEC-2023-298</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2023-298</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: safeurl-python&lt;/p&gt;
&lt;p&gt;isInList in the safeurl-python package before 1.2 for Python has an insufficiently restrictive regular expression for external domains, leading to SSRF.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: safeurl-python&lt;/p&gt;
&lt;p&gt;isInList in the safeurl-python package before 1.2 for Python has an insufficiently restrictive regular expression for external domains, leading to SSRF.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2023-298</guid>
    </item>
  </channel>
</rss>
