{"answers":{"affected":"3 open source packages ship an affected version, including openviking. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40525 in the wild and no public exploit code.","fix":"Upgrade openviking to 0.3.9 or later.","what":"CVE-2026-40525 is a critical authentication bypass vulnerability in volcengine OpenViking, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40525 and fix it if it is affected.\n\nWhat it is: CVE-2026-40525 is a critical authentication bypass vulnerability in volcengine OpenViking, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-40525 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- openviking (PyPI): affected all versions; fixed in 0.3.9\n- openviking (PyPI): affected all versions; fixed in 0.3.9\n- openviking (PyPI): affected all versions; fixed in 0.3.9\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-40525/ (Markdown: https://insights.sbomify.com/CVE-2026-40525/index.md)","id":"CVE-2026-40525","markdown":"https://insights.sbomify.com/CVE-2026-40525/index.md","name":"CVE-2026-40525","record":{"aliases":["GHSA-jgq2-vq69-gr6h","PYSEC-2026-438"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenViking AI service","requires_auth":"none","summary":"Remote attackers can bypass authentication in OpenViking VikingBot OpenAPI when API keys are unset, accessing privileged bot functions and sensitive data.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"openviking","vendor":"volcengine"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-636","name":"Not Failing Securely"}],"description":"OpenViking prior to version 0.3.9 contains an authentication bypass vulnerability in the VikingBot OpenAPI HTTP route surface where the authentication check fails open when the api_key configuration value is unset or empty. Remote attackers with network access to the exposed service can invoke privileged bot-control functionality without providing a valid X-API-Key header, including submitting attacker-controlled prompts, creating or using bot sessions, and accessing downstream tools, integrations, secrets, or data accessible to the bot.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OpenViking \u003c 0.3.9 Authentication Bypass via VikingBot OpenAPI","id":"CVE-2026-40525","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Volmarg Personal Management System Path Traversal via get-file Endpoint","id":"CVE-2026-40526"},"packages":[{"ecosystem":"PyPI","fixed":["0.3.9"],"introduced":["0"],"last_affected":[],"package":"openviking","purl":null,"source":"GHSA-jgq2-vq69-gr6h"},{"ecosystem":"PyPI","fixed":["0.3.9"],"introduced":["0"],"last_affected":[],"package":"openviking","purl":"pkg:pypi/openviking","source":"GHSA-jgq2-vq69-gr6h"},{"ecosystem":"PyPI","fixed":["0.3.9"],"introduced":["0"],"last_affected":[],"package":"openviking","purl":"pkg:pypi/openviking","source":"PYSEC-2026-438"}],"prev":{"headline":"FrontAccounting \u003c 2.4.20 SQL Injection via get_gl_transactions()","id":"CVE-2026-40524"},"products":["OpenViking"],"published":"2026-04-17","related":[{"cvss_score":8.4,"headline":"OpenViking .ovpack Import ZIP Slip Path Traversal","id":"CVE-2026-28518","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":6.9,"headline":"OpenViking \u003c 0.3.3 Missing Authorization via Task Polling","id":"CVE-2026-22680","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":6.9,"headline":"OpenViking 0.2.5 \u003c 0.2.14 Bot Proxy Endpoints Allow Unauthenticated Access","id":"CVE-2026-34999","kev_date_added":null,"published":"2026-04-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["volcengine"]},"summary":"Remote attackers can bypass authentication in OpenViking VikingBot OpenAPI when API keys are unset, accessing privileged bot functions and sensitive data.","url":"https://insights.sbomify.com/CVE-2026-40525/"}