A flaw has been found in AstrBotDevs AstrBot up to 4.25.5. This vulnerability affects the function OpenApiRoute.get_chat_sessions of the file astrbot/dashboard/routes/open_api.py of the component session-listing Endpoint. This manipulation of the argument Username causes authorization bypass. It is possible to initiate the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2026-16075
Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-07-18. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 12.3%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 21, 2026
Advisory Details (1)
Auto-updated Jul 18, 2026AstrBot: OpenAPI `chat`-scope API Key Can Enumerate Other Users' WebChat Sessions via Caller-Controlled `username` · GitHub
https://gist.github.com/YLChen-007/5fee3adfd95333b0f4eff8165af61f81Vendor Advisories for CVE-2026-16075(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-23 00:11 UTCEG score recompute
- 2026-07-23 00:10 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 04:38 UTCNVD updateCVSS v4 → 2.1
- 2026-07-21 03:31 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-07-20 17:55 UTCEG score recompute
- 2026-07-20 17:55 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 06:05 UTCEG score recompute
- 2026-07-18 06:02 UTCNVD updateCVSS v4 → 2.1
- 2026-07-18 04:20 UTCEG score recompute
- 2026-07-18 04:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639 · CWE-285
Frequently asked(5)
What is CVE-2026-16075?
When was CVE-2026-16075 disclosed?
Is CVE-2026-16075 actively exploited?
What is the CVSS score of CVE-2026-16075?
How do I remediate CVE-2026-16075?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16075
Is Your Infrastructure Affected by CVE-2026-16075?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.