<?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>Tue, 17 Nov 2026 04:46:15 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-386688</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-386688</link>
      <description>EUVD-2026-386688</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-386688</guid>
    </item>
    <item>
      <title>fkie_cve-2026-102603</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-102603</link>
      <description>&lt;p&gt;Gotify server is a simple server for sending and receiving messages in real-time per WebSocket. Prior to 3.0.0, the password change endpoint (POST /current/user/password) accepts a valid client token without requiring the account&amp;#39;s current password or another elevated authentication step. An attacker who obtains a client token can set a new password for the associated user, taking control of password authentication and forcing account recovery through an administrator or direct database access. This issue is fixed in version 3.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Gotify server is a simple server for sending and receiving messages in real-time per WebSocket. Prior to 3.0.0, the password change endpoint (POST /current/user/password) accepts a valid client token without requiring the account&amp;#39;s current password or another elevated authentication step. An attacker who obtains a client token can set a new password for the associated user, taking control of password authentication and forcing account recovery through an administrator or direct database access. This issue is fixed in version 3.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-102603</guid>
    </item>
    <item>
      <title>GHSA-3hcj-9m7p-wwm9 — Gotify: Insufficiently Protected Password Change endpoint</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3hcj-9m7p-wwm9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/gotify/server/v2, Go: github.com/gotify/server/v3&lt;/p&gt;
&lt;p&gt;The password change endpoint (`POST /current/user/password`) in Gotify versions &amp;lt;= 2.9.1 does not require knowledge of the current password. An attacker in possession of a valid client token can set a new password for the affected user. Recovering the account requires administrator intervention or direct database access.&lt;/p&gt;
&lt;p&gt;## PoC&lt;/p&gt;
&lt;p&gt;```bash
# Attacker has obtained a client token
# No prior password knowledge required
STOLEN_TOKEN=&amp;#34;Cxxxxxxxxxx&amp;#34;&lt;/p&gt;
&lt;p&gt;curl -X POST &amp;#34;http://gotify-host/current/user/password?token=${STOLEN_TOKEN}&amp;#34; \
  -H &amp;#34;Content-Type: application/json&amp;#34; \
  -d &amp;#39;{&amp;#34;pass&amp;#34;:&amp;#34;attacker_controls_this&amp;#34;}&amp;#39;
# Expected response:
# HTTP/1.1 200 OK
```&lt;/p&gt;
&lt;p&gt;## Mitigation&lt;/p&gt;
&lt;p&gt;- Upgrade to Gotify 3.0.0, which introduces step-up authentication: changing the  password now requires re-authenticating with the account password, or
- Restrict access to the state-changing endpoints under `/user` and  `/current/user` to trusted networks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/gotify/server/v2, Go: github.com/gotify/server/v3&lt;/p&gt;
&lt;p&gt;The password change endpoint (`POST /current/user/password`) in Gotify versions &amp;lt;= 2.9.1 does not require knowledge of the current password. An attacker in possession of a valid client token can set a new password for the affected user. Recovering the account requires administrator intervention or direct database access.&lt;/p&gt;
&lt;p&gt;## PoC&lt;/p&gt;
&lt;p&gt;```bash
# Attacker has obtained a client token
# No prior password knowledge required
STOLEN_TOKEN=&amp;#34;Cxxxxxxxxxx&amp;#34;&lt;/p&gt;
&lt;p&gt;curl -X POST &amp;#34;http://gotify-host/current/user/password?token=${STOLEN_TOKEN}&amp;#34; \
  -H &amp;#34;Content-Type: application/json&amp;#34; \
  -d &amp;#39;{&amp;#34;pass&amp;#34;:&amp;#34;attacker_controls_this&amp;#34;}&amp;#39;
# Expected response:
# HTTP/1.1 200 OK
```&lt;/p&gt;
&lt;p&gt;## Mitigation&lt;/p&gt;
&lt;p&gt;- Upgrade to Gotify 3.0.0, which introduces step-up authentication: changing the  password now requires re-authenticating with the account password, or
- Restrict access to the state-changing endpoints under `/user` and  `/current/user` to trusted networks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3hcj-9m7p-wwm9</guid>
    </item>
  </channel>
</rss>
