Vulnerability Lookup up to 5.5.1 Pub/Sub Interface /pubsub/subscribe authorization

Summaryinfo

A vulnerability classified as problematic was found in Vulnerability Lookup up to 5.5.1. The affected element is an unknown function of the file /pubsub/subscribe of the component Pub/Sub Interface. Executing a manipulation can lead to authorization. This vulnerability is tracked as CVE-2026-73405. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Vulnerability Lookup up to 5.5.1. It has been declared as problematic. This vulnerability affects an unknown function of the file /pubsub/subscribe of the component Pub/Sub Interface. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect confidentiality. CVE summarizes:

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 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's is_active and is_confirmed 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.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-73405 since 08/12/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are known technical details, but no exploit is available.

Applying the patch bef837242657acf680832be56b94428df130ed67 is able to eliminate this problem.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

• Vulnerability Lookup

Version

• 5.5.0
• 5.5.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion