# CVE-2026-22659: FlaskBB Authorization Bypass via Topic ID Manipulation

> Authenticated moderators can bypass permission checks to modify topics in forums they do not control by manipulating topic IDs in batch requests.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 10 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-9rjj-9p2h-6c55

## What is CVE-2026-22659?

CVE-2026-22659 is a high-severity missing authorization vulnerability in flaskbb, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FlaskBB through 2.2.0, fixed in commit acc88cf, contains an authorization bypass vulnerability that allows authenticated moderators to perform unauthorized actions on topics in forums they do not control by submitting crafted topic ID lists. Attackers can include a low-ID topic from a permitted forum as an anchor in a batch request, causing the permission check applied only to the first result to pass, and then execute lock, unlock, delete, or hide actions against topics in unmoderated forums.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-22659 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22659 is a high-severity missing authorization vulnerability in flaskbb, published on 10 Jul 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-22659 exists.

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

## Sources

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

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