Home/CVE/Sentry is a developer-first error tracking and performance monitoring tool. A critical vulnerability was discovered in t
CVE
CVE-2025-22146
Sentry is a developer-first error tracking and performance monitoring tool. A critical vulnerability was discovered in t
Sentry is a developer-first error tracking and performance monitoring tool. 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. The Sentry SaaS fix was deployed on Jan 14, 2025. For self hosted users.
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. There are no known workarounds for this vulnerability.
CRITICAL · CVSS 9.1
EPSS 0.0054
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2025-22146, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
8Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
T1040 · Network Sniffing T1134 · Access Token Manipulation T1185 · Browser Session Hijacking T1505.003 · Web Shell T1548 · Abuse Elevation Control Mechanism T1550.001 · Application Access Token T1557 · Adversary-in-the-Middle T1563 · Remote Service Session Hijacking
▤ Build a SIEM detection for these techniques
▤
CAPEC attack patterns
10Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-114 · Authentication Abuse CAPEC-CAPEC-115 · Authentication Bypass CAPEC-CAPEC-151 · Identity Spoofing CAPEC-CAPEC-194 · Fake the Source of Data CAPEC-CAPEC-22 · Exploiting Trust in Client CAPEC-CAPEC-57 · Utilizing REST's Trust in the System Resource to Obtain Sensitive Data CAPEC-CAPEC-593 · Session Hijacking CAPEC-CAPEC-633 · Token Impersonation CAPEC-CAPEC-650 · Upload a Web Shell to a Web Server CAPEC-CAPEC-94 · Adversary in the Middle (AiTM)
⬡
Weakness Classification
CWE-287Improper Authentication
▤
Affected Packages
1Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
PyPI
sentry
CRITICAL
fixed in 25.1.0
▣
Scoring & Timeline
9.1
CRITICAL · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
total
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
🔗
References & Sources
2Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.