Live › vulnerability › CVE-2026-111643
Go to dashboardMisaka Danmu Server <= 2.8.9 (self-hosted danmaku server) applies auth per endpoint, and several /api/ui routers have none. POST /api/ui/config-history/rollback takes an arbitrary key/value and upserts it into config with no login. An attacker sets ipWhitelist to their own /32, and check_ip_whitelist then treats them as admin on every protected endpoint. Trusted proxies and webhookApiKey can also be changed. Routers are registered by default. Other unauthenticated endpoints leak audit and server logs, list the library, and delete rows or clear audit logs.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| misaka_danmu_server | github | <= 2.8.9 | – |
Content-Type: application/json -d {}2.8.9)2.8.9 is the latest release)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Misaka Danmu Server through 2.8.9 contains an authentication bypass vulnerability that allows unauthenticated attackers to write arbitrary configuration keys via the unprotected POST /api/ui/config-history/rollback endpoint. Attackers can set the ipWhitelist key to their own /32 address, or alter trustedProxies and webhookApiKey, to access every protected endpoint as the administrator.
This page as .md · .json · in your agent: get_signal("CVE-2026-111643")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.