PT-2026-53601 · Pypi · Sentry

Published 2026-06-29 · Updated 2026-06-29

OSV

CVSS v3.1

9.1

Critical

Base vector

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Impact

A critical vulnerability was discovered in the SAML SSO implementation of Sentry. It was reported to us via our private bug bounty program.

The vulnerability allows an attacker to take over any user account by using a malicious SAML Identity Provider and another organization on the same Sentry instance. The victim email address must be known in order to exploit this vulnerability.

Patches

• Sentry SaaS: The fix was deployed on Jan 14, 2025.
• Self-Hosted Sentry: If only a single organization is allowed (SENTRY SINGLE ORGANIZATION = True), then no action is needed. Otherwise, users should upgrade to version 25.1.0 or higher.

Workarounds

No known workarounds.

References

• https://github.com/getsentry/sentry/pull/83407

Fix

Related Identifiers

PYSEC-2026-532

Affected Products

Sentry

References · 8

• https://osv.dev/vulnerability/PYSEC-2026-532 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2025-22146 · Security Note
• https://github.com/getsentry/sentry · Note
• https://github.com/getsentry/sentry/security/advisories/GHSA-7pq6-v88g-wf3w · Note
• https://github.com/getsentry/sentry/pull/83407 · Note
• https://github.com/getsentry/sentry/commit/6db508f7949d117c7dff748a3c82c3a272bf7cfd · Note
• https://pypi.org/project/sentry · Note
• https://github.com/advisories/GHSA-7pq6-v88g-wf3w · Note