{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8786 exists.","fix":"No fix has been published for CVE-2026-8786 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8786 is a medium-severity missing authorization vulnerability in Tencent WeKnora, published on 18 May 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-8786 and fix it if it is affected.\n\nWhat it is: CVE-2026-8786 is a medium-severity missing authorization vulnerability in Tencent WeKnora, published on 18 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8786 exists.\n\nAffected product: Tencent WeKnora. 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-8786/ (Markdown: https://insights.sbomify.com/CVE-2026-8786/index.md)","id":"CVE-2026-8786","markdown":"https://insights.sbomify.com/CVE-2026-8786/index.md","name":"CVE-2026-8786","record":{"aliases":["GHSA-4cvj-xf75-4wv6"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Tencent WeKnora","requires_auth":"low_privilege","summary":"Attackers can bypass authorization checks in the Config API to access knowledge bases without proper permissions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"weknora","vendor":"tencent"}],"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:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"A vulnerability has been found in Tencent WeKnora up to 0.3.6. Affected by this issue is the function getKnowledgeBaseForInitialization of the file internal/handler/initialization.go of the component Config API Endpoint. The manipulation of the argument kbId leads to authorization bypass. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Tencent WeKnora Config API Endpoint initialization.go getKnowledgeBaseForInitialization authorization","id":"CVE-2026-8786","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Firebase Support \u0026 Chat Management \u003c= 3.1.1 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation","id":"CVE-2026-8787"},"packages":[],"prev":{"headline":"projectworlds hospital-management-system-in-php GET Parameter update_info.php getAllPatientDetail sql injection","id":"CVE-2026-8785"},"products":["WeKnora"],"published":"2026-05-18","related":[{"cvss_score":10,"headline":"WeKnora: Remote Code Execution via SQL Injection Bypass in AI Database Query Tool","id":"CVE-2026-30860","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":10,"headline":"WeKnora: Remote Code Execution (RCE) via Command Injection in MCP Stdio Configuration Validation","id":"CVE-2026-30861","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":10,"headline":"WeKnora has Command Injection in MCP stdio test","id":"CVE-2026-22688","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":8.8,"headline":"WeKnora: Broken Access Control in Tenant Management","id":"CVE-2026-30855","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":6.9,"headline":"Tencent WeKnora test testEmbeddingModel server-side request forgery","id":"CVE-2025-11046","kev_date_added":null,"published":"2025-09-26"},{"cvss_score":6.5,"headline":"WeKnora: DNS Rebinding Vulnerability in web_fetch Tool Allows SSRF to Internal Resources","id":"CVE-2026-30858","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":5.9,"headline":"WeKnora: SSRF via Redirection","id":"CVE-2026-30247","kev_date_added":null,"published":"2026-03-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-18","vendors":["Tencent"]},"summary":"Attackers can bypass authorization checks in the Config API to access knowledge bases without proper permissions.","url":"https://insights.sbomify.com/CVE-2026-8786/"}