Security readout for executives and security teams
Plain-English summary
CVE-2026-16075 is an authorization bypass in AstrBot’s session-listing API. A logged-in user may be able to manipulate a username parameter to view chat sessions they should not access. The issue is rated medium, but exposure matters because it can disclose conversation/session metadata or content depending on deployment.
Executive priority
Treat as a near-term remediation item for any exposed AstrBot instance. It is not currently evidenced as mass exploited, but the public exploit and authorization-bypass nature make delay risky where chat session data is sensitive.
Technical view
AstrBotDevs AstrBot versions 4.25.0 through 4.25.5 are reported affected. The flaw is in OpenApiRoute.get_chat_sessions in astrbot/dashboard/routes/open_api.py. VulDB maps it to CWE-285 and CWE-639. CVSS v4.0 is 5.3: network reachable, low complexity, low privileges required, no user interaction, limited confidentiality impact.
Likely exposure
Systems running AstrBot 4.25.0 through 4.25.5 with the dashboard/open API reachable by authenticated users are the primary exposure. Internet-facing administrative or API interfaces increase business risk. Sources do not identify other affected products or versions.
Exploitation context
The source bundle says a public exploit exists and the attack can be initiated remotely. It also indicates low privileges are required. There is no CISA KEV listing in the provided data and no cited evidence of active exploitation in the wild.
Researcher notes
Evidence is currently driven by VulDB and CVE references. The vendor reportedly did not respond before disclosure, and the provided sources do not name a fixed version. Avoid assuming data impact beyond the documented low confidentiality impact unless confirmed in your environment.
Mitigation direction
- Identify AstrBot deployments and confirm whether versions 4.25.0 through 4.25.5 are present.
- Check AstrBotDevs guidance for a patched release or official workaround.
- Restrict dashboard and open API access to trusted networks or VPN.
- Limit accounts with access to the affected API until remediation is available.
- Review logs for unusual session-listing requests or unexpected username targeting.
Validation and detection
- Inventory AstrBot versions across production, staging, and developer systems.
- Confirm whether the session-listing endpoint is reachable from untrusted networks.
- Verify access controls prevent users from viewing other users’ sessions.
- Review authentication and authorization logs for suspicious session enumeration patterns.
- Track vendor advisories and retest after applying any official fix.
Public sources used
- CVE Program
- CVE List V5
- VDB-379790 | AstrBotDevs AstrBot session-listing Endpoint open_api.py OpenApiRoute.get_chat_sessions authorization
- VDB-379790 | CTI Indicators (IOB, IOC, IOA)
- CVE-2026-16075 | CVE Analysis and Report
- Submit #852863 | AstrBotDevs AstrBot <= 4.25.5 Authorization Bypass Through User-Controlled Key (CWE-639)
- Public exploit reference
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-285: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-16075 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P——VulDBCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R2.81.4VulDBCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R2.81.4VulDBAV:N/AC:L/Au:S/C:P/I:N/A:N/E:POC/RL:ND/RC:UR82.9VulDBVulnerability scoring details
Base CVSS 4.0 score
5.3MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R
Base CVSS 3.0 score
4.3MediumVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R
Base CVSS 2.0 score
4MediumVector: AV:N/AC:L/Au:S/C:P/I:N/A:N/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineVulDB
Advisory disclosed
- Source timelineVulDB
VulDB entry created
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineVulDB
VulDB entry last update
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- VDB-379790 | AstrBotDevs AstrBot session-listing Endpoint open_api.py OpenApiRoute.get_chat_sessions authorizationCVE reference, VulDB · vdb-entry, technical-description
- VDB-379790 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- CVE-2026-16075 | CVE Analysis and ReportCVE reference, VulDB · third-party-advisory
- Submit #852863 | AstrBotDevs AstrBot <= 4.25.5 Authorization Bypass Through User-Controlled Key (CWE-639)CVE reference, VulDB · third-party-advisory
- https://gist.github.com/YLChen-007/5fee3adfd95333b0f4eff8165af61f81CVE reference, VulDB · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.