<?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>Mon, 05 Oct 2026 19:35:54 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-342444</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-342444</link>
      <description>EUVD-2026-342444</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-342444</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54693</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54693</link>
      <description>&lt;p&gt;ZITADEL is an open source identity management platform. From 2.43.0 through 2.71.19, from 3.0.0 until 3.4.11, and from 4.0.0 until 4.15.1, the email and phone self-management API paths in internal/command/user_v2_email.go, internal/command/user_v2_phone.go, and internal/command/user_v2_human.go allowed users to request returned verification codes without the required permission, allowing users to claim ownership of email addresses or phone numbers they do not control and bypass email-based or phone-based security policies. This issue is fixed in versions 3.4.11 and 4.15.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ZITADEL is an open source identity management platform. From 2.43.0 through 2.71.19, from 3.0.0 until 3.4.11, and from 4.0.0 until 4.15.1, the email and phone self-management API paths in internal/command/user_v2_email.go, internal/command/user_v2_phone.go, and internal/command/user_v2_human.go allowed users to request returned verification codes without the required permission, allowing users to claim ownership of email addresses or phone numbers they do not control and bypass email-based or phone-based security policies. This issue is fixed in versions 3.4.11 and 4.15.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54693</guid>
    </item>
    <item>
      <title>GHSA-jq8w-8q2f-ffm9 — ZITADEL Users Can Self-Verify Email/Phone via API</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jq8w-8q2f-ffm9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zitadel/zitadel&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A vulnerability in Zitadel&amp;#39;s self-management capability allowed users to mark their email and phone as verified without going through an actual verification process.&lt;/p&gt;
&lt;p&gt;While [`GHSA-282g-fhmx-xf54`](https://github.com/zitadel/zitadel/security/advisories/GHSA-282g-fhmx-xf54) (CVE-2026-27946, &amp;#34;Users Can Self-Verify Email/Phone via UpdateHumanUser API&amp;#34;) closed the path that let any authenticated user mark an arbitrary email or phone as verified on their own account by calling `UpdateHumanUser` with `email.is_verified: true`, additional paths were discovered.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Zitadel provides an API for managing users. The API also allows users to self-manage their own data including updating the email and phone.&lt;/p&gt;
&lt;p&gt;Due to an improper permission check, the API allowed returning the verification code for the email and phone to the own user.
This allows users to claim ownership of an email or phone they do not control and potentially bypass email-based security policies.&lt;/p&gt;
&lt;p&gt;Note that when changing another user&amp;#39;s email or phone, regardless of the verification flag, the permissions were correctly checked.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;Systems running one of the following versions are affected:
- **4.x**: `4.0.0` through `4.15.0` (including RC versions)
- **3.x**: `3.0.0` through `3.4.10` (including RC versions)
- **2.x**: `2.43.0` through `2.71.19`&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring the correct permissio…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zitadel/zitadel&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A vulnerability in Zitadel&amp;#39;s self-management capability allowed users to mark their email and phone as verified without going through an actual verification process.&lt;/p&gt;
&lt;p&gt;While [`GHSA-282g-fhmx-xf54`](https://github.com/zitadel/zitadel/security/advisories/GHSA-282g-fhmx-xf54) (CVE-2026-27946, &amp;#34;Users Can Self-Verify Email/Phone via UpdateHumanUser API&amp;#34;) closed the path that let any authenticated user mark an arbitrary email or phone as verified on their own account by calling `UpdateHumanUser` with `email.is_verified: true`, additional paths were discovered.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Zitadel provides an API for managing users. The API also allows users to self-manage their own data including updating the email and phone.&lt;/p&gt;
&lt;p&gt;Due to an improper permission check, the API allowed returning the verification code for the email and phone to the own user.
This allows users to claim ownership of an email or phone they do not control and potentially bypass email-based security policies.&lt;/p&gt;
&lt;p&gt;Note that when changing another user&amp;#39;s email or phone, regardless of the verification flag, the permissions were correctly checked.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;Systems running one of the following versions are affected:
- **4.x**: `4.0.0` through `4.15.0` (including RC versions)
- **3.x**: `3.0.0` through `3.4.10` (including RC versions)
- **2.x**: `2.43.0` through `2.71.19`&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring the correct permissio…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jq8w-8q2f-ffm9</guid>
    </item>
  </channel>
</rss>
