How many CVEs have patched handle_async_deletion?

1 published CVEs changed handle_async_deletion in getsentry/sentry, in 2 distinct patches totalling 15 changed lines, between 2025 and 2025.

What is the latest CVE that changed handle_async_deletion?

CVE-2025-53099 (Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation), published 2025-07-01, changed lines 262 to 276 of src/sentry/models/apitoken.py.

How does handle_async_deletion compare to the rest of getsentry/sentry?

getsentry/sentry has 19 CVEs with a located fix in total; 1 of them changed handle_async_deletion.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

getsentry/sentry

Function

handle_async_deletion

Name: handle_async_deletion in getsentry/sentry: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

src/sentry/models/apitoken.py

Last patched July 1, 2025

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

15

Lines changed

Added plus removed

2025

Years

By CVE publication date

Overview

handle_async_deletion in getsentry/sentry was changed by 1 published CVE fixes in 2025, in 2 distinct patches that added or removed 15 lines in total.

getsentry/sentry has 19 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed handle_async_deletion, newest first, with the lines each fix touched.

Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation
CVE-2025-53099 · lines 262–276 · +15 −0
Medium · CVSS 5.5
EPSS 0.8%2025-07-01

Get an alert when the next CVE fix lands in getsentry/sentry, with the patched functions.

Monitor sentry CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1from_grantsrc/sentry/models/apitoken.py1 CVEs · 2 patches2025

Other hotspots in the repository

Functions in getsentry/sentry changed by the most CVE fixes.

handle_unknown_identity2 CVEs · src/sentry/auth/helper.py dispatch1 CVEs · src/sentry/auth/providers/saml2/provider.py _validate_superuser1 CVEs · src/sentry/api/endpoints/auth_index.py strip_op_from_post1 CVEs · src/sentry/auth/providers/saml2/provider.py _login1 CVEs · src/sentry/auth/helper.py _build_confirmation_response1 CVEs · src/sentry/auth/helper.py

All patched functions in getsentry/sentry

Frequently asked questions

Common questions about CVE fixes to handle_async_deletion.

How many CVEs have patched handle_async_deletion?: 1 published CVEs changed handle_async_deletion in getsentry/sentry, in 2 distinct patches totalling 15 changed lines, between 2025 and 2025.
What is the latest CVE that changed handle_async_deletion?: CVE-2025-53099 (Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation), published 2025-07-01, changed lines 262 to 276 of src/sentry/models/apitoken.py.
How does handle_async_deletion compare to the rest of getsentry/sentry?: getsentry/sentry has 19 CVEs with a located fix in total; 1 of them changed handle_async_deletion.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track getsentry/sentry CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing