# CVE-2026-111644: Misaka Danmu Server through 2.8.9 Missing Authentication on /api/ui Routes

> Unauthenticated attackers can access sensitive audit logs and modify or delete data on Misaka Danmu Server due to missing authentication on specific API routes.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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:** 16 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-c5c3-5f6v-5chh

## What is CVE-2026-111644?

CVE-2026-111644 is a medium-severity missing authorization vulnerability in l429609201 misaka_danmu_server, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Misaka Danmu Server through 2.8.9 contains a missing authentication vulnerability that allows unauthenticated attackers to access audit, diagnostics, data-check, scan-index and health routes under /api/ui lacking the get_current_user dependency. Attackers can read audit logs with login IPs, server logs and environment paths, delete episode rows, clear media-server mappings, and wipe audit history.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-111644 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111644 is a medium-severity missing authorization vulnerability in l429609201 misaka_danmu_server, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111644 exists.

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

## Sources

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

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