# CVE-2026-57447: Discourse Doc Categories: Doc category index refresh leaks private topic titles

> An attacker with edit access to the index topic can view titles of private or restricted topics they are not authorized to see.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-x63p-48vw-8r64

## What is CVE-2026-57447?

CVE-2026-57447 is a medium-severity vulnerability in discourse-doc-categories, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Discourse Doc Categories is a plugin for organizing Discourse topics as documentation. Prior to the verified source fix, the doc category index refresh resolves linked titles for private messages or restricted category topics without enforcing the viewer's authorization. A user who can edit the index topic can use this behavior to learn titles that the user is not authorized to view, although the advisory does not establish access to topic contents. This vulnerability is addressed by commit b15d4de02ad29d7c9525346afee51fef4a2c605a.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-57447 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57447 is a medium-severity vulnerability in discourse-doc-categories, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57447 in the wild and no public exploit code.

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

## Sources

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

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