<?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 02:46:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-7819 — pgAdmin 4: Symbolic-link path traversal in File Manager allows arbitrary file write</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-7819</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pgadmin.org pgAdmin 4&lt;/p&gt;
&lt;p&gt;Symbolic-link path traversal (CWE-61, CWE-22) in pgAdmin 4 File Manager.&lt;/p&gt;
&lt;p&gt;check_access_permission used os.path.abspath, which resolves &amp;#39;..&amp;#39; but does not resolve symbolic links, while the subsequent kernel write follows symlinks. An authenticated user could plant a symbolic link inside their own storage directory pointing outside it and induce pgAdmin to write to any path reachable by the pgAdmin process.&lt;/p&gt;
&lt;p&gt;Fix switches the access check to os.path.realpath for both source and destination, and adds an _open_upload_target helper that opens the target with O_NOFOLLOW (mode 0o600) to close the leaf-component TOCTOU between the access check and the open. File mode is hardened from 0o644 to 0o600.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.15.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pgadmin.org pgAdmin 4&lt;/p&gt;
&lt;p&gt;Symbolic-link path traversal (CWE-61, CWE-22) in pgAdmin 4 File Manager.&lt;/p&gt;
&lt;p&gt;check_access_permission used os.path.abspath, which resolves &amp;#39;..&amp;#39; but does not resolve symbolic links, while the subsequent kernel write follows symlinks. An authenticated user could plant a symbolic link inside their own storage directory pointing outside it and induce pgAdmin to write to any path reachable by the pgAdmin process.&lt;/p&gt;
&lt;p&gt;Fix switches the access check to os.path.realpath for both source and destination, and adds an _open_upload_target helper that opens the target with O_NOFOLLOW (mode 0o600) to close the leaf-component TOCTOU between the access check and the open. File mode is hardened from 0o644 to 0o600.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.15.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-7819</guid>
    </item>
    <item>
      <title>GHSA-hr4r-fwpv-c95j — pgAdmin 4 File Manager has symbolic-link path traversal</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hr4r-fwpv-c95j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pgadmin4&lt;/p&gt;
&lt;p&gt;Symbolic-link path traversal (CWE-61, CWE-22) in pgAdmin 4 File Manager.&lt;/p&gt;
&lt;p&gt;check_access_permission used os.path.abspath, which resolves &amp;#39;..&amp;#39; but does not resolve symbolic links, while the subsequent kernel write follows symlinks. An authenticated user could plant a symbolic link inside their own storage directory pointing outside it and induce pgAdmin to write to any path reachable by the pgAdmin process.&lt;/p&gt;
&lt;p&gt;Fix switches the access check to os.path.realpath for both source and destination, and adds an _open_upload_target helper that opens the target with O_NOFOLLOW (mode 0o600) to close the leaf-component TOCTOU between the access check and the open. File mode is hardened from 0o644 to 0o600.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.15.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pgadmin4&lt;/p&gt;
&lt;p&gt;Symbolic-link path traversal (CWE-61, CWE-22) in pgAdmin 4 File Manager.&lt;/p&gt;
&lt;p&gt;check_access_permission used os.path.abspath, which resolves &amp;#39;..&amp;#39; but does not resolve symbolic links, while the subsequent kernel write follows symlinks. An authenticated user could plant a symbolic link inside their own storage directory pointing outside it and induce pgAdmin to write to any path reachable by the pgAdmin process.&lt;/p&gt;
&lt;p&gt;Fix switches the access check to os.path.realpath for both source and destination, and adds an _open_upload_target helper that opens the target with O_NOFOLLOW (mode 0o600) to close the leaf-component TOCTOU between the access check and the open. File mode is hardened from 0o644 to 0o600.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.15.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hr4r-fwpv-c95j</guid>
    </item>
  </channel>
</rss>
