<?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 14:17:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-41236 — Froxlor has privilege escalation in SSH key synchronization via symlinked `authorized_keys` path</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-41236</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; froxlor&lt;/p&gt;
&lt;p&gt;Froxlor is open source server administration software. Version 2.3.6 contains a symlink-following flaw in the root-owned SSH key synchronization path used for customer FTP users. The provisioning code appends public keys to `~/.ssh/authorized_keys` under a customer-controlled home directory without verifying that the target path is not a symbolic link. If an attacker controls a shell-enabled customer account and can modify files inside the assigned home directory, the attacker can replace `~/.ssh/authorized_keys` with a symlink to `/root/.ssh/authorized_keys`. When Froxlor&amp;#39;s privileged cron task later synchronizes SSH keys, it appends the attacker-supplied key into root&amp;#39;s authorized key file, resulting in root SSH access. Version 2.3.7 contains a patch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; froxlor&lt;/p&gt;
&lt;p&gt;Froxlor is open source server administration software. Version 2.3.6 contains a symlink-following flaw in the root-owned SSH key synchronization path used for customer FTP users. The provisioning code appends public keys to `~/.ssh/authorized_keys` under a customer-controlled home directory without verifying that the target path is not a symbolic link. If an attacker controls a shell-enabled customer account and can modify files inside the assigned home directory, the attacker can replace `~/.ssh/authorized_keys` with a symlink to `/root/.ssh/authorized_keys`. When Froxlor&amp;#39;s privileged cron task later synchronizes SSH keys, it appends the attacker-supplied key into root&amp;#39;s authorized key file, resulting in root SSH access. Version 2.3.7 contains a patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-41236</guid>
    </item>
  </channel>
</rss>
