CVE-2026-18852

LOWPre-NVD 3.33.3—
EchelonGraph scoreHIGH confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-08-05. a secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability has been found in epsilla-cloud vectordb up to 0.3.18/df5a5f5afb85a2376a0f2f316c79dea9b2c6ac7a. This impacts the function SplitTokens/ShuntingYard of the file engine/query/expr/expr.cpp of the component Filter Parser. Such manipulation leads to improper check for unusual conditions. The attack needs to be performed locally. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
3.3
EG Score
3.3(high)
EG Risk
31(Track)
EG Risk 31/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 computed
Severity33% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 12, 2026

References (6)

Vendor Advisories for CVE-2026-18852(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 33× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 19:12 UTCEG score recompute
  4. 2026-08-18 19:12 UTCGHSA enrichment
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 20:10 UTCEG score recompute
  9. 2026-08-15 20:10 UTCGHSA enrichment
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-12 21:08 UTCEG score recompute
  13. 2026-08-12 21:08 UTCGHSA enrichment
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 13:31 UTCEG score recompute
  16. 2026-08-11 13:31 UTCGHSA enrichment
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-08 14:30 UTCEG score recompute
  21. 2026-08-08 14:30 UTCGHSA enrichment
  22. 2026-08-06 13:46 UTCEPSS rescore
  23. 2026-08-05 19:17 UTCEPSS rescore
  24. 2026-08-05 15:28 UTCEG score recompute
  25. 2026-08-05 15:28 UTCGHSA enrichment
Show 8 more
  1. 2026-08-05 15:26 UTCNVD updateCVSS v4 → 1.9
  2. 2026-08-05 14:37 UTCEG score recompute
  3. 2026-08-05 14:37 UTCGHSA enrichment
  4. 2026-08-05 14:35 UTCMITRE cvelistV5CVSS v4 → 4.8
  5. 2026-08-05 00:20 UTCEG score recompute
  6. 2026-08-05 00:18 UTCNVD updateCVSS v4 → 1.9
  7. 2026-08-04 23:21 UTCEG score recompute
  8. 2026-08-04 23:20 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18852?
CVE-2026-18852 is a low vulnerability published on August 4, 2026. A vulnerability has been found in epsilla-cloud vectordb up to 0.3.18/df5a5f5afb85a2376a0f2f316c79dea9b2c6ac7a. This impacts the function SplitTokens/ShuntingYard of the file engine/query/expr/expr.cpp of the component Filter Parser. Such manipulation leads to improper check for unusual conditions.…
When was CVE-2026-18852 disclosed?
CVE-2026-18852 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18852 actively exploited?
CVE-2026-18852 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-18852?
CVE-2026-18852 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-18852?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18852, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-18852

Explore →

Is Your Infrastructure Affected by CVE-2026-18852?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs