<?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://vulnerability.circl.lu</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, 30 Sep 2026 15:51:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64640 — Apache Polaris: register endpoint reads attacker-controlled storage location before allowed-locations validation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64640</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Polaris&lt;/p&gt;
&lt;p&gt;Apache Polaris did not consistently validate storage locations supplied during table and view registration.&lt;/p&gt;
&lt;p&gt;An authenticated principal with permission to register a table or view could, depending on the affected release and registration path, cause Polaris to use the catalog&amp;#39;s storage credentials to read a caller-selected Iceberg metadata file before verifying that the file was within the catalog&amp;#39;s allowed storage locations.&lt;/p&gt;
&lt;p&gt;If the catalog&amp;#39;s underlying credentials could read an object outside that boundary, this could disclose limited information from the object.&lt;/p&gt;
&lt;p&gt;Polaris could also accept registration metadata located within an allowed location that contained references to storage locations outside the allowed boundary.&lt;/p&gt;
&lt;p&gt;This second condition did not itself cause Polaris to read the referenced external locations during registration.&lt;/p&gt;
&lt;p&gt;The demonstrated impact is limited to confidentiality.&lt;/p&gt;
&lt;p&gt;No unauthorized data modification or availability impact has been demonstrated.&lt;/p&gt;
&lt;p&gt;The server-side read requires a deployment using S3 credential vending and an object outside the allowed locations that the catalog&amp;#39;s underlying storage credentials can read.&lt;/p&gt;
&lt;p&gt;Exploitation requires an authenticated principal with table- or view-registration privileges.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Polaris&lt;/p&gt;
&lt;p&gt;Apache Polaris did not consistently validate storage locations supplied during table and view registration.&lt;/p&gt;
&lt;p&gt;An authenticated principal with permission to register a table or view could, depending on the affected release and registration path, cause Polaris to use the catalog&amp;#39;s storage credentials to read a caller-selected Iceberg metadata file before verifying that the file was within the catalog&amp;#39;s allowed storage locations.&lt;/p&gt;
&lt;p&gt;If the catalog&amp;#39;s underlying credentials could read an object outside that boundary, this could disclose limited information from the object.&lt;/p&gt;
&lt;p&gt;Polaris could also accept registration metadata located within an allowed location that contained references to storage locations outside the allowed boundary.&lt;/p&gt;
&lt;p&gt;This second condition did not itself cause Polaris to read the referenced external locations during registration.&lt;/p&gt;
&lt;p&gt;The demonstrated impact is limited to confidentiality.&lt;/p&gt;
&lt;p&gt;No unauthorized data modification or availability impact has been demonstrated.&lt;/p&gt;
&lt;p&gt;The server-side read requires a deployment using S3 credential vending and an object outside the allowed locations that the catalog&amp;#39;s underlying storage credentials can read.&lt;/p&gt;
&lt;p&gt;Exploitation requires an authenticated principal with table- or view-registration privileges.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64640</guid>
    </item>
  </channel>
</rss>
