Quick answers
- Is CVE-2026-16075 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16075 being exploited in the wild.
- How severe is CVE-2026-16075?
- Medium severity, with a CVSS score of 4.3, published 18 July 2026.
- Which products and versions are affected?
- AstrBotDevs AstrBot <= 4.25.5.
- Is there a fix for CVE-2026-16075?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-16075 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16075?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authorization bypass (CWE-639) exists in AstrBot up to version 4.25.5 within the `OpenApiRoute.get_chat_sessions` function in `astrbot/dashboard/routes/open_api.py`. While the middleware correctly authenticates the API key and enforces the 'chat' scope, the business logic in the session-listing endpoint fails to bind the request to the authenticated principal. Instead, it uses an attacker-controlled `username` query parameter to filter database results. A remote attacker with a valid chat-scope API key can exploit this to retrieve session metadata (IDs, timestamps, and creator names) for any known or guessable username. As of the advisory date, the vendor has not responded to the disclosure.
Affected products
- AstrBotDevs AstrBot <= 4.25.5
Timeline
- 2026-06-09: disclosed: Initial researcher disclosure via GitHub Gist
- 2026-07-18: advisory: CVE published to NVD/VulDB