Service crash via unmatched parenthesis stack pop
Published Aug 4, 2026 · Updated Aug 4, 2026
Improper exceptional-condition handling in Epsilla Vector Database 0.3.0 through 0.3.18 allows local users to crash the service. SplitTokens accepts an unmatched closing parenthesis, and ShuntingYard then unconditionally pops an empty operator stack. A low-privileged local user must reach a code path that parses a malformed filter; the demonstrated consequence is process termination without data disclosure or modification.
Summary
What happened
Improper exceptional-condition handling in Epsilla Vector Database 0.3.0 through 0.3.18 allows local users to crash the service. SplitTokens accepts an unmatched closing parenthesis, and ShuntingYard then unconditionally pops an empty operator stack. A low-privileged local user must reach a code path that parses a malformed filter; the demonstrated consequence is process termination without data disclosure or modification.
The record
- CVE
- CVE-2026-18852
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Vendor
- Epsilla
- Product
- Epsilla Vector Database
- Classifications
- CWE-754, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 4, 2026CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.3.0
- Affected versionversion=0.3.1
- Affected versionversion=0.3.10
- Affected versionversion=0.3.11
- Affected versionversion=0.3.12
- Affected versionversion=0.3.13
- Affected versionversion=0.3.14
- Affected versionversion=0.3.15
- Affected versionversion=0.3.16
- Affected versionversion=0.3.17
- Affected versionversion=0.3.18
- Affected versionversion=0.3.2
- Affected versionversion=0.3.3
- Affected versionversion=0.3.4
- Affected versionversion=0.3.5
- Affected versionversion=0.3.6
- Affected versionversion=0.3.7
- Affected versionversion=0.3.8
- Affected versionversion=0.3.9
- Affected versionversion=df5a5f5afb85a2376a0f2f316c79dea9b2c6ac7a
What conditions does exploitation require?
What is affected?
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
- VectorDB filter parser unmatched parenthesis PoCproof 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