← Back to results
Vulnerability record · public intelligence
CVE-2025-53099
MEDIUM

Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation

Published Jul 1, 2025 · Updated Nov 3, 2026

Severity · CVSSMEDIUM · Not scored
Known exploitationNot listed
EPSS / likelihood0.80%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Sentry is a developer-first error tracking and performance monitoring tool. Prior to version 25.5.0, an attacker with a malicious OAuth application registered with Sentry can take advantage of a race condition and improper handling of authorization code within Sentry to maintain persistence to a user's account. With a specially timed requests and redirect flows, an attacker could generate multiple authorization codes that could be used to exchange for access and refresh tokens. This was possible even after de-authorizing the particular application. This issue has been patched in version 25.5.0. Self-hosted Sentry users should upgrade to version 25.5.0 or higher. Sentry SaaS users do not need to take any action.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
MEDIUM
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗
  3. Source repository ↗
  4. Source repository ↗
  5. Source repository ↗
  6. Patch commit ↗
  7. Patch commit ↗
  8. Patch commit ↗

Record history

Published Jul 1, 2025 · Last refreshed Nov 3, 2026