<?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-10-04T12:44:25.142123+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-318996</id>
    <title>EUVD-2026-318996</title>
    <updated>2026-10-04T12:44:25.206058+00:00</updated>
    <content>EUVD-2026-318996</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-318996"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-22706</id>
    <title>fkie_cve-2026-22706</title>
    <updated>2026-10-04T12:44:25.206104+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Strapi is an open source headless content management system. In Strapi versions prior to 5.33.3, changing or resetting a user's password did not invalidate the user's existing refresh-token sessions by default. The refresh-token invalidation step in the users-permissions and admin authentication controllers was conditional on a caller-supplied `deviceId`. When a password change or reset request did not include a `deviceId`, no refresh tokens were revoked, leaving every prior session active. An attacker who had previously obtained a refresh token could continue minting new access tokens after the legitimate user reset their password, allowing persistent unauthorized access for the lifetime of the refresh token (up to 30 days by default). Rotating credentials no longer terminated an active attacker session, defeating password reset as a containment measure. The patch in version 5.33.3 invalidates all refresh tokens associated with the user on every password change and password reset, regardless of whether a `deviceId` is supplied. A new device-scoped session is then issued to the caller as part of the response.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-22706"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hvp3-26wx-g2w4</id>
    <title>GHSA-hvp3-26wx-g2w4 — Strapi: Password Reset Does Not Revoke Existing Refresh Sessions</title>
    <updated>2026-10-04T12:44:25.206178+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @strapi/admin, npm: @strapi/plugin-users-permissions</p>
<p>### Summary of CVE-2026-22706 Vulnerability Details</p>
<p>- CVE: CVE-2026-22706
- CVSS v3.1 Vector: `CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N` (2.1 — Low)
- Affected Versions: `@strapi/admin` and `@strapi/plugin-users-permissions` &lt;=5.33.2
- How to Patch: Immediately update your Strapi to &gt;=5.33.3</p>
<p>### Description of CVE-2026-22706</p>
<p>In Strapi versions prior to 5.33.3, changing or resetting a user's password did not invalidate the user's existing refresh-token sessions by default. The refresh-token invalidation step in the users-permissions and admin authentication controllers was conditional on a caller-supplied `deviceId`. When a password change or reset request did not include a `deviceId`, no refresh tokens were revoked, leaving every prior session active.</p>
<p>An attacker who had previously obtained a refresh token could continue minting new access tokens after the legitimate user reset their password, allowing persistent unauthorized access for the lifetime of the refresh token (up to 30 days by default). Rotating credentials no longer terminated an active attacker session, defeating password reset as a containment measure.</p>
<p>The patch invalidates all refresh tokens associated with the user on every password change and password reset, regardless of whether a `deviceId` is supplied. A new device-scoped session is then issued to the caller as part of the response.</p>
<p>### IoC's for CVE-2026-22706</p>
<p>Indicators that an instance running an unpatched version may have…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hvp3-26wx-g2w4"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1552</id>
    <title>WID-SEC-W-2026-1552 — Strapi: Mehrere Schwachstellen</title>
    <updated>2026-10-04T12:44:25.206243+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Strapi ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen, Administratorrechte zu erlangen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder Sicherheitsmaßnahmen zu umgehen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1552"/>
  </entry>
</feed>
