# CVE-2026-81826: Flowintel Fails to Invalidate Active Sessions After Password Change

> Attackers with stolen session tokens retain access after password changes because sessions are not invalidated, requiring a patch to enforce session termination.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-m2jr-93w5-4c48

## What is CVE-2026-81826?

CVE-2026-81826 is a critical vulnerability in flowintel, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected versions of Flowintel do not revoke existing authenticated sessions when a user’s password is changed.

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:

“session keeps working until it expires.”

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().

Version impacted >=3.3.0

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration), CWE-384 (Session Fixation)

## Which versions are affected by CVE-2026-81826?


## How do I fix CVE-2026-81826?

No fix has been published for CVE-2026-81826 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-81826 being exploited?

There is no known exploitation of CVE-2026-81826 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81826 and fix it if it is affected.

What it is: CVE-2026-81826 is a critical vulnerability in flowintel, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81826 in the wild and no public exploit code.

Affected product: flowintel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81826/ (Markdown: https://insights.sbomify.com/CVE-2026-81826/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81826
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81826
- OSV: https://osv.dev/vulnerability/CVE-2026-81826

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81826/
Summaries are generated and may contain mistakes; the official description above is the record.