<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T04:56:55.088230+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-386688</id>
    <title>EUVD-2026-386688</title>
    <updated>2026-11-17T04:56:55.143034+00:00</updated>
    <content>EUVD-2026-386688</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-386688"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-102603</id>
    <title>fkie_cve-2026-102603</title>
    <updated>2026-11-17T04:56:55.143070+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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'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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-102603"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3hcj-9m7p-wwm9</id>
    <title>GHSA-3hcj-9m7p-wwm9 — Gotify: Insufficiently Protected Password Change endpoint</title>
    <updated>2026-11-17T04:56:55.143107+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/gotify/server/v2, Go: github.com/gotify/server/v3</p>
<p>The password change endpoint (`POST /current/user/password`) in Gotify versions &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.</p>
<p>## PoC</p>
<p>```bash
# Attacker has obtained a client token
# No prior password knowledge required
STOLEN_TOKEN="Cxxxxxxxxxx"</p>
<p>curl -X POST "http://gotify-host/current/user/password?token=${STOLEN_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"pass":"attacker_controls_this"}'
# Expected response:
# HTTP/1.1 200 OK
```</p>
<p>## Mitigation</p>
<p>- 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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3hcj-9m7p-wwm9"/>
  </entry>
</feed>
