{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-73405 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-73405 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-73405 is a medium-severity missing authorization vulnerability in vulnerability-lookup, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73405 and fix it if it is affected.\n\nWhat it is: CVE-2026-73405 is a medium-severity missing authorization vulnerability in vulnerability-lookup, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-73405 in the wild and no public exploit code.\n\nAffected product: vulnerability-lookup. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73405/ (Markdown: https://insights.sbomify.com/CVE-2026-73405/index.md)","id":"CVE-2026-73405","markdown":"https://insights.sbomify.com/CVE-2026-73405/index.md","name":"CVE-2026-73405","record":{"aliases":["GHSA-8gv5-4q99-4cxm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Vulnerability-Lookup","requires_auth":"low_privilege","summary":"Attackers with unconfirmed accounts can access restricted SSE streams, exposing unmoderated data due to missing active status checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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/\u003ctopic\u003e endpoint.\n\nThe 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.\n\nBecause 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.\n\nThe vulnerability results from inconsistent authorization enforcement between the REST API and the SSE streaming interface.\n\nThe 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Authorization Bypass in SSE Pub/Sub Allows Unconfirmed Accounts to Access Stream Events in vulnerability-lookup","id":"CVE-2026-73405","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Budibase: Unauthenticated user information disclosure via public tenant user lookup endpoint","id":"CVE-2026-73406"},"packages":[],"prev":{"headline":"WordPress MasterStudy LMS plugin \u003c= 3.7.41 - Broken Access Control vulnerability","id":"CVE-2026-73404"},"products":["vulnerability-lookup"],"published":"2026-08-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-12","vendors":["vulnerability-lookup"]},"summary":"Attackers with unconfirmed accounts can access restricted SSE streams, exposing unmoderated data due to missing active status checks.","url":"https://insights.sbomify.com/CVE-2026-73405/"}