<?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:57:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-73405 — Authorization Bypass in SSE Pub/Sub Allows Unconfirmed Accounts to Access Stream Events in vulnerability-lookup</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-73405</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; vulnerability-lookup&lt;/p&gt;
&lt;p&gt;An authorization bypass vulnerability in Vulnerability-Lookup allowed inactive or unconfirmed accounts to subscribe to Server-Sent Events (SSE) streams through the /pubsub/subscribe/&amp;lt;topic&amp;gt; endpoint.&lt;/p&gt;
&lt;p&gt;The token_required decorator used by the Pub/Sub interface authenticated requests solely by matching the X-API-KEY header against an existing user API key. Unlike the REST API authentication mechanism, it did not verify the account&amp;#39;s is_active and is_confirmed state.&lt;/p&gt;
&lt;p&gt;Because the self-registration process issues an API key before account confirmation is completed, an attacker could create an account and immediately use the resulting API key to access Pub/Sub topics that should only be available to active, confirmed users. This could expose stream events that would otherwise be inaccessible through the REST API, including newly submitted or not-yet-moderated data such as comments.&lt;/p&gt;
&lt;p&gt;The vulnerability results from inconsistent authorization enforcement between the REST API and the SSE streaming interface.&lt;/p&gt;
&lt;p&gt;The patch corrects the issue by requiring accounts to be both active and confirmed before permitting access to Pub/Sub streams, bringing the SSE authorization boundary in line with the REST API.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; vulnerability-lookup&lt;/p&gt;
&lt;p&gt;An authorization bypass vulnerability in Vulnerability-Lookup allowed inactive or unconfirmed accounts to subscribe to Server-Sent Events (SSE) streams through the /pubsub/subscribe/&amp;lt;topic&amp;gt; endpoint.&lt;/p&gt;
&lt;p&gt;The token_required decorator used by the Pub/Sub interface authenticated requests solely by matching the X-API-KEY header against an existing user API key. Unlike the REST API authentication mechanism, it did not verify the account&amp;#39;s is_active and is_confirmed state.&lt;/p&gt;
&lt;p&gt;Because the self-registration process issues an API key before account confirmation is completed, an attacker could create an account and immediately use the resulting API key to access Pub/Sub topics that should only be available to active, confirmed users. This could expose stream events that would otherwise be inaccessible through the REST API, including newly submitted or not-yet-moderated data such as comments.&lt;/p&gt;
&lt;p&gt;The vulnerability results from inconsistent authorization enforcement between the REST API and the SSE streaming interface.&lt;/p&gt;
&lt;p&gt;The patch corrects the issue by requiring accounts to be both active and confirmed before permitting access to Pub/Sub streams, bringing the SSE authorization boundary in line with the REST API.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-73405</guid>
    </item>
  </channel>
</rss>
