<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 17:19:41 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-210664</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-210664</link>
      <description>EUVD-2026-210664</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-210664</guid>
    </item>
    <item>
      <title>fkie_cve-2025-22146</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-22146</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-22146</guid>
    </item>
    <item>
      <title>GHSA-7pq6-v88g-wf3w — Sentry's improper authentication on SAML SSO process allows user impersonation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7pq6-v88g-wf3w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: sentry&lt;/p&gt;
&lt;p&gt;### Impact
A critical vulnerability was discovered in the SAML SSO implementation of Sentry. It was reported to us via our private bug bounty program.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches
- [Sentry SaaS](https://sentry.io): The fix was deployed on Jan 14, 2025.
- [Self-Hosted Sentry](https://github.com/getsentry/self-hosted): 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.&lt;/p&gt;
&lt;p&gt;### Workarounds
No known workarounds.&lt;/p&gt;
&lt;p&gt;### References
- https://github.com/getsentry/sentry/pull/83407&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: sentry&lt;/p&gt;
&lt;p&gt;### Impact
A critical vulnerability was discovered in the SAML SSO implementation of Sentry. It was reported to us via our private bug bounty program.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches
- [Sentry SaaS](https://sentry.io): The fix was deployed on Jan 14, 2025.
- [Self-Hosted Sentry](https://github.com/getsentry/self-hosted): 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.&lt;/p&gt;
&lt;p&gt;### Workarounds
No known workarounds.&lt;/p&gt;
&lt;p&gt;### References
- https://github.com/getsentry/sentry/pull/83407&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7pq6-v88g-wf3w</guid>
    </item>
    <item>
      <title>PYSEC-2026-532 — Sentry's improper authentication on SAML SSO process allows user impersonation</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-532</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: sentry&lt;/p&gt;
&lt;p&gt;### Impact
A critical vulnerability was discovered in the SAML SSO implementation of Sentry. It was reported to us via our private bug bounty program.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches
- [Sentry SaaS](https://sentry.io): The fix was deployed on Jan 14, 2025.
- [Self-Hosted Sentry](https://github.com/getsentry/self-hosted): 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.&lt;/p&gt;
&lt;p&gt;### Workarounds
No known workarounds.
 
### References
- https://github.com/getsentry/sentry/pull/83407&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: sentry&lt;/p&gt;
&lt;p&gt;### Impact
A critical vulnerability was discovered in the SAML SSO implementation of Sentry. It was reported to us via our private bug bounty program.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches
- [Sentry SaaS](https://sentry.io): The fix was deployed on Jan 14, 2025.
- [Self-Hosted Sentry](https://github.com/getsentry/self-hosted): 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.&lt;/p&gt;
&lt;p&gt;### Workarounds
No known workarounds.
 
### References
- https://github.com/getsentry/sentry/pull/83407&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-532</guid>
    </item>
  </channel>
</rss>
