<?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://db.gcve.eu</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, 04 Nov 2026 23:18:06 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-117649</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-117649</link>
      <description>&lt;p&gt;The issue timeline API and the web issue page hid cross-reference events that point at issues the reader cannot access, but not &amp;#34;dependency added&amp;#34; and &amp;#34;dependency removed&amp;#34; events. When a readable issue had been linked as a dependency to an issue in a repository the reader cannot access, for example a private repository, any reader of the first issue, including anonymous users of a public repository, received the linked issue&amp;#39;s current title, body, state, labels, poster and attachment names through the API, and its repository, number and title on the web page. Creating the link requires access to both issues; comments and attachment downloads of the linked issue stayed protected. Dependency events are now filtered with the same read permission check; a related exposure of unlinked attachment metadata through hidden dependency placeholders was already fixed in 28.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The issue timeline API and the web issue page hid cross-reference events that point at issues the reader cannot access, but not &amp;#34;dependency added&amp;#34; and &amp;#34;dependency removed&amp;#34; events. When a readable issue had been linked as a dependency to an issue in a repository the reader cannot access, for example a private repository, any reader of the first issue, including anonymous users of a public repository, received the linked issue&amp;#39;s current title, body, state, labels, poster and attachment names through the API, and its repository, number and title on the web page. Creating the link requires access to both issues; comments and attachment downloads of the linked issue stayed protected. Dependency events are now filtered with the same read permission check; a related exposure of unlinked attachment metadata through hidden dependency placeholders was already fixed in 28.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-117649</guid>
    </item>
  </channel>
</rss>
