CVE-2026-71424 onyx-dot-app CVE debrief

Who should care

Defenders responsible for Onyx AI platform deployments, especially those with BASIC_ACCESS users, should assess exposure and prioritize verification of Onyx server versions. This includes reviewing and updating access controls, monitoring for potential unauthorized access, and implementing compensating controls for exposed systems. Security teams and vulnerability management teams should also review the supplied official advisory or CVE record to validate,

Why it matters

CVE-2026-71424 is a critical vulnerability in Onyx AI platform that allows unauthorized access to OAuth headers. Defenders should prioritize verifying exposure and assessing potential impact.

• Potential unauthorized access to OAuth headers
• Increased risk of authentication bypass
• Possible lateral movement within Onyx deployments
• Need for verification of Onyx server versions and exposure

Technical summary

The vulnerability is caused by improper token storage in the Onyx backend, specifically in the OnyxTokenStorage.set_tokens and OnyxTokenStorage.set_client_info functions. This allows any BASIC_ACCESS user to access another user's OAuth Authorization header. The issue is fixed in Onyx versions 3.1.10, 3.2.14, and 4.0.0. However, specific details about exploitation or victim impact are not provided in the source corpus. Affected product deployments should prioritize verification of Onyx server versions and assess potential exposure.

Defensive priority

Defenders should prioritize verifying exposure of Onyx servers, especially those with BASIC_ACCESS users, and assess the impact of potential unauthorized access to OAuth headers.

Recommended defensive actions

• Verify Onyx server versions and ensure they are updated to 3.1.10, 3.2.14, or 4.0.0.
• Assess exposure of Onyx servers, especially those with BASIC_ACCESS users.
• Monitor for potential unauthorized access to OAuth headers.
• Review and update access controls for Onyx servers.
• Perform a thorough review of Onyx server configurations to identify potential security risks.
• Implement compensating controls for exposed systems while remediation is scheduled and verified.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The vulnerability is confirmed in Onyx versions prior to 3.1.10, 3.2.14, and 4.0.0. The issue is fixed in these versions. However, specific details about exploitation or victim impact are not provided in the source corpus.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.