How many CVEs have patched _build_confirmation_response?

1 published CVEs changed _build_confirmation_response in getsentry/sentry, in 2 distinct patches totalling 2 changed lines, between 2026 and 2026.

What is the latest CVE that changed _build_confirmation_response?

CVE-2026-102899 (Sentry: Improper authentication on SAML SSO process allows user identity linking), published 2026-10-14, changed lines 508 to 515 of src/sentry/auth/helper.py.

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

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

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

_build_confirmation_response

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

src/sentry/auth/helper.py

Last patched October 14, 2026

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

2

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_build_confirmation_response in getsentry/sentry was changed by 1 published CVE fixes in 2026, in 2 distinct patches that added or removed 2 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 _build_confirmation_response, newest first, with the lines each fix touched.

Sentry: Improper authentication on SAML SSO process allows user identity linking
CVE-2026-102899 · lines 508–515 · +2 −0
High · CVSS 7.6
EPSS 0.4%2026-10-14

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.

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 _import1 CVEs · src/sentry/backup/imports.py

All patched functions in getsentry/sentry

Frequently asked questions

Common questions about CVE fixes to _build_confirmation_response.

How many CVEs have patched _build_confirmation_response?: 1 published CVEs changed _build_confirmation_response in getsentry/sentry, in 2 distinct patches totalling 2 changed lines, between 2026 and 2026.
What is the latest CVE that changed _build_confirmation_response?: CVE-2026-102899 (Sentry: Improper authentication on SAML SSO process allows user identity linking), published 2026-10-14, changed lines 508 to 515 of src/sentry/auth/helper.py.
How does _build_confirmation_response compare to the rest of getsentry/sentry?: getsentry/sentry has 19 CVEs with a located fix in total; 1 of them changed _build_confirmation_response.
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