CVE-2026-73405: Authorization Bypass in SSE Pub/Sub Allows Unconfirmed Accounts to Access Stream Events in vulnerability-lookup
An authorization bypass vulnerability in Vulnerability-Lookup allowed inactive or unconfirmed accounts to subscribe to Server-Sent Events (SSE) streams through the /pubsub/subscribe/<topic> endpoint.
The tokenrequired 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's isactive and isconfirmed state.
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.
The vulnerability results from inconsistent authorization enforcement between the REST API and the SSE streaming interface.
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Update the SSE Pub/Sub authorization boundary so the Pub/Sub interface validates the requesting account is both active and confirmed (in addition to the X-API-KEY match), before allowing access to the /pubsub/subscribe/<topic> endpoint.
vulnerability-lookup SSE Pub/Sub authorization account authorization checks for Pub/Sub access = require both is_active=true and is_confirmed=true before permitting access to /pubsub/subscribe/<topic>
Event History
Frequently Asked Questions
What is the severity of CVE-2026-73405?
CVE-2026-73405 has a risk score of 43, indicating a moderate level of severity.
How do I fix CVE-2026-73405?
To fix CVE-2026-73405, ensure that the authorization checks are properly implemented for inactive or unconfirmed accounts accessing the SSE Pub/Sub functionality.
What systems are affected by CVE-2026-73405?
CVE-2026-73405 affects the Vulnerability-Lookup software, specifically the Server-Sent Events (SSE) Pub/Sub feature.
What are the potential consequences of CVE-2026-73405?
The potential consequences of CVE-2026-73405 include unauthorized access to stream events by inactive or unconfirmed accounts, which may expose sensitive data.
When was CVE-2026-73405 published?
CVE-2026-73405 was published on August 12, 2026.