<?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-06T17:12:20.064859+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/cve-2026-81826</id>
    <title>CVE-2026-81826 — Flowintel Fails to Invalidate Active Sessions After Password Change</title>
    <updated>2026-10-06T17:12:20.066439+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> flowintel</p>
<p>Affected versions of Flowintel do not revoke existing authenticated sessions when a user’s password is changed.</p>
<p>This means that if an attacker already possesses a valid session—for example, from prior access or a stolen session token—the victim changing their password does not terminate that attacker’s access. The session remains usable until it expires naturally. The upstream commit describes this directly as:</p>
<p>“session keeps working until it expires.”</p>
<p>The fix detects password changes and explicitly invokes _invalidate_user_sessions(user.id) after the database update. This is applied in both edit_user_core() and admin_edit_user_core().</p>
<p>Version impacted &gt;=3.3.0</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-81826"/>
  </entry>
</feed>
