Sentry vulnerable to incorrect credential validation on OAuth token requests
GHSA-hgj4-h2x3-rfx4 · CVE-2023-39531 · PYSEC-2026-1915
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Impact
An attacker with sufficient client-side exploits could retrieve a valid access token for another user during the OAuth token exchange due to incorrect credential validation. The client ID must be known and the API application must have already been authorized on the targeted user account.
Remediation
- Sentry SaaS customers do not need to take any action. Those with the highest risk will be contacted directly by Sentry.
- Self-hosted installations should upgrade to version 23.7.2 or higher.
Workarounds
There are no direct workarounds, but users should review applications authorized on their account (User Settings > Authorized Applications) and remove any that are no longer needed.
Ready to move
Start Securing
Free, no credit card | First findings in minutes