<?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>Wed, 07 Oct 2026 16:06:44 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-364333</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-364333</link>
      <description>EUVD-2026-364333</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-364333</guid>
    </item>
    <item>
      <title>fkie_cve-2026-12071</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-12071</link>
      <description>&lt;p&gt;The Webbox of TeamDavid by Tobit Laboratories AG constructs redirect URLs using user-supplied input, 
which is appended to the redirect target in a 302 HTTP response. By 
using URL-encoded characters such as “%2e” (representing a dot), an 
attacker can manipulate the portion of the URL following the top-level 
domain (TLD). If a similar, registerable TLD exists (for example, if 
“.com” is the application’s domain, and “.company” is available for 
registration), an attacker can craft a URL to redirect users to a 
malicious “.company” domain. By using URL-encoded line feeds, it becomes
 possible to insert arbitrary response headers in the server&amp;#39;s HTTP 
response.&lt;/p&gt;
&lt;p&gt;This issue affects TeamDavid before Rollout 528.&lt;/p&gt;
&lt;p&gt;Starting with Rollout 528 (June 30, 2026), the affected functionality is disabled by default and the vulnerabilities are therefore no longer exposed through this functionality.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Webbox of TeamDavid by Tobit Laboratories AG constructs redirect URLs using user-supplied input, 
which is appended to the redirect target in a 302 HTTP response. By 
using URL-encoded characters such as “%2e” (representing a dot), an 
attacker can manipulate the portion of the URL following the top-level 
domain (TLD). If a similar, registerable TLD exists (for example, if 
“.com” is the application’s domain, and “.company” is available for 
registration), an attacker can craft a URL to redirect users to a 
malicious “.company” domain. By using URL-encoded line feeds, it becomes
 possible to insert arbitrary response headers in the server&amp;#39;s HTTP 
response.&lt;/p&gt;
&lt;p&gt;This issue affects TeamDavid before Rollout 528.&lt;/p&gt;
&lt;p&gt;Starting with Rollout 528 (June 30, 2026), the affected functionality is disabled by default and the vulnerabilities are therefore no longer exposed through this functionality.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-12071</guid>
    </item>
    <item>
      <title>GHSA-jrwc-g36x-gqc7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jrwc-g36x-gqc7</link>
      <description>&lt;p&gt;The Webbox of TeamDavid by Tobit Laboratories AG constructs redirect URLs using user-supplied input, 
which is appended to the redirect target in a 302 HTTP response. By 
using URL-encoded characters such as “%2e” (representing a dot), an 
attacker can manipulate the portion of the URL following the top-level 
domain (TLD). If a similar, registerable TLD exists (for example, if 
“.com” is the application’s domain, and “.company” is available for 
registration), an attacker can craft a URL to redirect users to a 
malicious “.company” domain. By using URL-encoded line feeds, it becomes
 possible to insert arbitrary response headers in the server&amp;#39;s HTTP 
response.&lt;/p&gt;
&lt;p&gt;This issue affects TeamDavid through Rollout 524.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Webbox of TeamDavid by Tobit Laboratories AG constructs redirect URLs using user-supplied input, 
which is appended to the redirect target in a 302 HTTP response. By 
using URL-encoded characters such as “%2e” (representing a dot), an 
attacker can manipulate the portion of the URL following the top-level 
domain (TLD). If a similar, registerable TLD exists (for example, if 
“.com” is the application’s domain, and “.company” is available for 
registration), an attacker can craft a URL to redirect users to a 
malicious “.company” domain. By using URL-encoded line feeds, it becomes
 possible to insert arbitrary response headers in the server&amp;#39;s HTTP 
response.&lt;/p&gt;
&lt;p&gt;This issue affects TeamDavid through Rollout 524.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jrwc-g36x-gqc7</guid>
    </item>
  </channel>
</rss>
