CVE-2026-73405
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk21th percentile - higher than 21% of all known CVEs
Summary
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 only checked the X-API-KEY header against an existing user API key, without verifying the account's is_active and is_confirmed state. An attacker could create an account and immediately use the API key to access Pub/Sub topics that should only be available to active, confirmed users.
Risk Assessment
Risk of exposing stream events, including newly submitted or not-yet-moderated data such as comments, that would otherwise be inaccessible through the REST API. This could lead to confidentiality and integrity breaches.
Recommendation
Apply the patch that requires accounts to be both active and confirmed before permitting access to Pub/Sub streams. Update the system to a patched version.
Other vulnerabilities in Vulnerability-Lookup
See all- CVE-2026-101041Medium
The account recovery (password reset) functionality in the vulnerability-lookup web application contains a TOCTOU race condition in the consumption of single-use recovery tokens. Two concurrent HTTP requests with the same valid token can both pass verification before either transaction commits, allowing both to set their own password on the target account. Additionally, a secondary defect in the same endpoint allows a valid recovery link to set an empty or trivially short password because form validation is not invoked.
- CVE-2026-73432Medium
SSRF vulnerability in the remote-instance synchronization functionality of Vulnerability-Lookup. Remote instance addresses were validated only for basic URL syntax before being stored, and the synchronization worker later dereferenced them without network-boundary restrictions, following redirects without revalidation. An authenticated administrator with admin:access permission could configure a remote instance pointing to internal, loopback, link-local, or cloud metadata services.
- CVE-2026-73431High
Vulnerability-Lookup has an authentication weakness in account activation and password recovery, where tokens are reusable and not purpose-bound. An attacker who obtains a valid link can repeatedly change the password and take control of the account.
- CVE-2026-73374Medium
A stored cross-site scripting (XSS) vulnerability existed in Vulnerability-Lookup in the render_tag_badges Jinja filter used to display reference tags associated with vulnerability records. Values from containers.cna.references[].tags[] were directly interpolated into HTML badge elements and wrapped in markupsafe.Markup, bypassing Jinja's automatic HTML escaping. An authenticated user with permissions to create or modify vulnerability records could submit a crafted reference tag through the CNA API containing arbitrary HTML or JavaScript-capable markup.
- CVE-2025-60249Medium
vulnerability-lookup 2.16.0 contains an XSS vulnerability in bundle.py, comment.py, and user.py, which can be exploited by a user of a vulnerability-lookup instance who can add bundles, comments, or sightings. The vulnerability stems from insufficient sanitization of user-supplied input before rendering in templates and tables, allowing injection of arbitrary JavaScript.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS