User Impersonation Affecting sentry package, versions [21.12.0,]


Severity

Recommended
0.0
critical
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.03% (9th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-PYTHON-SENTRY-16415488
  • published4 May 2026
  • disclosed30 Apr 2026
  • creditjaydns

Introduced: 30 Apr 2026

NewCVE-2026-42354  (opens in a new tab)
CWE-290  (opens in a new tab)

How to fix?

A fix was pushed into the master branch but not yet published.

Overview

Affected versions of this package are vulnerable to User Impersonation through the AuthHelper SSO setup flow in the auth helper pipeline. An attacker can link a Sentry account to a different identity by supplying an IdP assertion email that resolves to another user during provider setup. This causes the newly configured SSO identity to be attached to the wrong account, letting the attacker assume an unintended user identity and leaving the organization’s SSO configuration bound to the wrong member.

Notes

  • The takeover path depends on the victim email already being known and on the IdP assertion resolving to an existing Sentry user record during setup; if the assertion email does not map to a user, the misbinding condition described in the advisory does not arise.
  • While a fix was included in 26.4.1, Sentry stopped publishing packages to PyPI since 23.7.1; for additional information, see this issue in the maintainer's repository.

Workarounds

  • Enable user account two-factor authentication, especially for organization admins. This prevents an attacker from completing authentication as a victim account even if they can trigger the SSO linking flow.

CVSS Base Scores

version 4.0
version 3.1