{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-71424 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-71424 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-71424 is a critical vulnerability in onyx-dot-app onyx, published on 17 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-71424 and fix it if it is affected.\n\nWhat it is: CVE-2026-71424 is a critical vulnerability in onyx-dot-app onyx, published on 17 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-71424 in the wild and no public exploit code.\n\nAffected product: onyx-dot-app onyx. 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-71424/ (Markdown: https://insights.sbomify.com/CVE-2026-71424/index.md)","id":"CVE-2026-71424","markdown":"https://insights.sbomify.com/CVE-2026-71424/index.md","name":"CVE-2026-71424","record":{"aliases":["GHSA-q62f-rv3h-f822"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Onyx AI platform","requires_auth":"low_privilege","summary":"Attackers can steal other users' OAuth tokens via exposed API endpoints, potentially leading to account takeover in the Onyx AI platform.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Onyx is an open-source AI platform. Prior to 3.1.10, 3.2.14, and 4.0.0, Onyx's GET /api/mcp/servers and GET /api/mcp/servers/persona/{persona_id} endpoints expose another user's OAuth Authorization header because OnyxTokenStorage.set_tokens and OnyxTokenStorage.set_client_info in backend/onyx/server/features/mcp/api.py copy per-user tokens into a shared admin MCPConnectionConfig row and _db_mcp_server_to_api_mcp_server returns that row through auth_template.headers to any BASIC_ACCESS user. This issue is fixed in versions 3.1.10, 3.2.14, and 4.0.0.","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":"Onyx: Cross-user OAuth-token leak via /api/mcp/servers* for per-user MCP servers","id":"CVE-2026-71424","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"GetSimple CMS: Authenticated Stored Local File Inclusion (LFI) via page \"template\" field","id":"CVE-2026-71426"},"packages":[],"prev":{"headline":"Suricata doh2: crafted HTTP/2 DATA frames can cause quadratic CPU consumption","id":"CVE-2026-71418"},"products":["onyx"],"published":"2026-08-17","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":"total"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["onyx-dot-app"]},"summary":"Attackers can steal other users' OAuth tokens via exposed API endpoints, potentially leading to account takeover in the Onyx AI platform.","url":"https://insights.sbomify.com/CVE-2026-71424/"}