Description
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.
Published: 2026-08-12
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows an attacker to create a new user account, receive an API key before the account is confirmed, and use that key to subscribe to Server‑Sent Events streams through /pubsub/subscribe/<topic>. The API key is accepted regardless of the account’s is_active or is_confirmed status, enabling access to data that should only be visible to fully active and confirmed users. This read‑only bypass can expose new or not‑yet‑moderated content such as comments, compromising the confidentiality of the event stream.

Affected Systems

The affected software is the vulnerability‑lookup product, version information was not provided in the advisory. All installations that use the SSE Pub/Sub interface and generate API keys during self‑registration are potentially impacted.

Risk and Exploitability

With a CVSS score of 5.3 the vulnerability is considered moderate, but the lack of an EPSS score means exploitation likelihood is unknown. It is not currently listed in CISA’s KEV catalog. Likely attack steps involve registering an account, awaiting confirmation, and immediately calling the SSE subscription endpoint with the issued API key. The vulnerability stems from inconsistent authorization between the REST API and SSE interface, which can be exploited without special privileges or advanced skills.

Generated by OpenCVE AI on August 13, 2026 at 00:28 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the vendor‑supplied patch that requires accounts to be active and confirmed before allowing SSE subscription.
  • Revoke all pre‑patch API keys, especially those issued to accounts that were not confirmed at the time of issuance.
  • Add an additional status check (is_active and is_confirmed) in the SSE token validator to enforce the same rules as the REST API until the patch is applied.

Generated by OpenCVE AI on August 13, 2026 at 00:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 13 Aug 2026 10:15:00 +0000

Type Values Removed Values Added
First Time appeared Circl
Circl vulnerability-lookup
Vendors & Products Circl
Circl vulnerability-lookup

Wed, 12 Aug 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 12 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Authorization Bypass in SSE Pub/Sub Allows Unconfirmed Accounts to Access Stream Events in vulnerability-lookup
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Circl Vulnerability-lookup
cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-08-12T17:10:19.723Z

Reserved: 2026-08-12T14:15:51.914Z

Link: CVE-2026-73405

cve-icon Vulnrichment

Updated: 2026-08-12T17:10:15.944Z

cve-icon NVD

Status : Deferred

Published: 2026-08-12T15:18:33.343

Modified: 2026-08-26T16:49:18.760

Link: CVE-2026-73405

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T09:48:35Z

Weaknesses