<?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, 04 Oct 2026 17:56:41 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-325202</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-325202</link>
      <description>EUVD-2026-325202</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-325202</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41237</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41237</link>
      <description>&lt;p&gt;Froxlor is open source server administration software. In version 2.3.6 and earlier, the LOC record regex uses `\s+` which matches newlines (allowing embedded newlines to pass), TLSA `matchingType=0` has no upper bound on hex data length, and all validators return raw input without zone-file escaping. Version 2.3.7 contains an updated patch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Froxlor is open source server administration software. In version 2.3.6 and earlier, the LOC record regex uses `\s+` which matches newlines (allowing embedded newlines to pass), TLSA `matchingType=0` has no upper bound on hex data length, and all validators return raw input without zone-file escaping. Version 2.3.7 contains an updated patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41237</guid>
    </item>
    <item>
      <title>GHSA-j6fm-9rfm-j5hx — Froxlor has an incomplete fix for CVE-2026-30932</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j6fm-9rfm-j5hx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: froxlor/froxlor&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The LOC record regex uses `\s+` which matches newlines (allowing embedded newlines to pass), TLSA `matchingType=0` has no upper bound on hex data length, and all validators return raw input without zone-file escaping.&lt;/p&gt;
&lt;p&gt;### Affected Package&lt;/p&gt;
&lt;p&gt;- **Ecosystem:** Other
- **Package:** froxlor
- **Affected versions:** all versions before fix commit b34829262dc3
- **Patched versions:** &amp;gt;= commit b34829262dc3&lt;/p&gt;
&lt;p&gt;### Severity&lt;/p&gt;
&lt;p&gt;Medium -- CVSS&lt;/p&gt;
&lt;p&gt;### CWE&lt;/p&gt;
&lt;p&gt;CWE-74 -- Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;DNS record content is concatenated directly into bind9 zone files at `DnsEntry.php` line 83. Before the fix, LOC/RP/SSHFP/TLSA records had no content validation at all, enabling zone file injection via embedded newlines.&lt;/p&gt;
&lt;p&gt;The fix adds format-specific regexes and field validation but has gaps: the LOC regex&amp;#39;s `\s+` matches newlines in PHP&amp;#39;s PCRE engine, allowing a LOC record with a newline between fields to pass validation but produce multiple lines in the zone file. TLSA `matchingType=0` only requires `len(data) &amp;gt;= 2` with no upper bound, enabling arbitrarily large payloads. All validators return raw input without zone-file escaping.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```python
#!/usr/bin/env python3
&amp;#34;&amp;#34;&amp;#34;
CVE-2026-30932 - Incomplete DNS Record Content Validation in froxlor/froxlor&lt;/p&gt;
&lt;p&gt;Affected component: lib/Froxlor/Api/Commands/DomainZones.php
Vulnerability type: Input Validation / DNS Zone File Injection
Patch: https://github.com/froxl…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: froxlor/froxlor&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The LOC record regex uses `\s+` which matches newlines (allowing embedded newlines to pass), TLSA `matchingType=0` has no upper bound on hex data length, and all validators return raw input without zone-file escaping.&lt;/p&gt;
&lt;p&gt;### Affected Package&lt;/p&gt;
&lt;p&gt;- **Ecosystem:** Other
- **Package:** froxlor
- **Affected versions:** all versions before fix commit b34829262dc3
- **Patched versions:** &amp;gt;= commit b34829262dc3&lt;/p&gt;
&lt;p&gt;### Severity&lt;/p&gt;
&lt;p&gt;Medium -- CVSS&lt;/p&gt;
&lt;p&gt;### CWE&lt;/p&gt;
&lt;p&gt;CWE-74 -- Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;DNS record content is concatenated directly into bind9 zone files at `DnsEntry.php` line 83. Before the fix, LOC/RP/SSHFP/TLSA records had no content validation at all, enabling zone file injection via embedded newlines.&lt;/p&gt;
&lt;p&gt;The fix adds format-specific regexes and field validation but has gaps: the LOC regex&amp;#39;s `\s+` matches newlines in PHP&amp;#39;s PCRE engine, allowing a LOC record with a newline between fields to pass validation but produce multiple lines in the zone file. TLSA `matchingType=0` only requires `len(data) &amp;gt;= 2` with no upper bound, enabling arbitrarily large payloads. All validators return raw input without zone-file escaping.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```python
#!/usr/bin/env python3
&amp;#34;&amp;#34;&amp;#34;
CVE-2026-30932 - Incomplete DNS Record Content Validation in froxlor/froxlor&lt;/p&gt;
&lt;p&gt;Affected component: lib/Froxlor/Api/Commands/DomainZones.php
Vulnerability type: Input Validation / DNS Zone File Injection
Patch: https://github.com/froxl…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j6fm-9rfm-j5hx</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1737 — Froxlor: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1737</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Froxlor ausnutzen, um seine Privilegien zu erhöhen, um Informationen offenzulegen, um Dateien zu manipulieren, und um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Froxlor ausnutzen, um seine Privilegien zu erhöhen, um Informationen offenzulegen, um Dateien zu manipulieren, und um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1737</guid>
    </item>
  </channel>
</rss>
