Cross-user model-list disclosure via static cache key
Published Jul 9, 2026 · Updated Jul 9, 2026
Information disclosure in Open WebUI 0.6.27 and later before 0.10.0 allows remote authenticated users to receive another user's model list. The get_all_models handlers pass a per-user lambda as aiocache's static key rather than key_builder, causing every caller to reuse one cache entry. Exploitation requires differently permissioned users and closely timed requests; only model existence and names are exposed during the default one-second TTL.
Summary
What happened
Information disclosure in Open WebUI 0.6.27 and later before 0.10.0 allows remote authenticated users to receive another user's model list. The get_all_models handlers pass a per-user lambda as aiocache's static key rather than key_builder, causing every caller to reuse one cache entry. Exploitation requires differently permissioned users and closely timed requests; only model existence and names are exposed during the default one-second TTL.
The record
- CVE
- CVE-2026-59213
- Published
- Jul 9, 2026
- Updated
- Jul 9, 2026
- Vendor
- Open WebUI
- Product
- Open WebUI
- Classifications
- CWE-524, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2026CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.6.27, < 0.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory default-configuration reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo