CVE-2026-71424
Onyx broken access control
- Published17 Aug 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://github.com/onyx-dot-app/onyx/commit/3f3d79d1a7722fdc84a1c61c8aa830d890017e9e
- https://github.com/onyx-dot-app/onyx/commit/4001cedd0a8968723bfe95dd188914ed56777910
- https://github.com/onyx-dot-app/onyx/commit/b103937888fd5008067c2bb6eb6e5424576394f2
- https://github.com/onyx-dot-app/onyx/pull/11238
- https://github.com/onyx-dot-app/onyx/pull/11242
- https://github.com/onyx-dot-app/onyx/pull/11243
- https://github.com/onyx-dot-app/onyx/releases/tag/v4.0.0
- https://github.com/onyx-dot-app/onyx/security/advisories/GHSA-q62f-rv3h-f822
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-71424 being actively exploited?
CVE-2026-71424 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.49%.
How severe is CVE-2026-71424?
CVE-2026-71424 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.49% probability of exploitation.
How do I fix CVE-2026-71424?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-71424 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.