# CVE-2026-46656: Bludit CMS has improper authorization and mediation failure leading to persistent ghost sessions

> Deleted users retain active sessions, allowing unauthorized access to the Bludit CMS system.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-rpq2-j9w3-h4jw

## What is CVE-2026-46656?

CVE-2026-46656 is a high-severity authentication bypass vulnerability in bludit, published on 8 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Bludit is a content management system. Versions prior to 3.22.0 have a Broken Access Control flaw where active sessions remain valid even after the corresponding user account has been  physically deleted from the database. This "Ghost Session" allows revoked users to maintain full unauthorized access to the system. Version 3.22.0 fixes the issue.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-46656 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46656 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46656 is a high-severity authentication bypass vulnerability in bludit, published on 8 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46656 exists.

Affected product: bludit. 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-46656/ (Markdown: https://insights.sbomify.com/CVE-2026-46656/index.md)
```

## Sources

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

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