SurrealDB versions before 2.2.2 contain a memory exhaustion vulnerability in the string::replace function that fails to restrict resulting string length when using regex patterns. An authenticated attacker can craft a malicious query to exhaust server memory through unbounded string allocations, causing denial of service.
CVE-2025-71395
HIGHPre-NVD 7.17.1Trending — 4 sources updated this week
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(low)
- EPSS
- 14.5%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 18, 2026Patch available. Sources: github.
generic
SurrealDB before 2.2.2 Memory Exhaustion via string::replace | Advisories | VulnCheck
https://www.vulncheck.com/advisories/surrealdb-before-memory-exhaustion-via-string-replacegithub Patch Available
Memory exhaustion via string::replace using regex · Advisory · surrealdb/surrealdb · GitHub
https://github.com/surrealdb/surrealdb/security/advisories/GHSA-3633-g6mg-p6qqVendor Advisories for CVE-2025-71395(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| surrealdb | — | 2.2.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× 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-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 16:06 UTCEG score recompute
- 2026-07-18 16:05 UTCGHSA enrichment
- 2026-07-18 13:40 UTCEG score recompute
- 2026-07-18 13:39 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2025-71395?
CVE-2025-71395 is a high vulnerability published on July 18, 2026. SurrealDB versions before 2.2.2 contain a memory exhaustion vulnerability in the string::replace function that fails to restrict resulting string length when using regex patterns. An authenticated attacker can craft a malicious query to exhaust server memory through unbounded string allocations,…
When was CVE-2025-71395 disclosed?
CVE-2025-71395 was first published in the National Vulnerability Database on July 18, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71395 actively exploited?
CVE-2025-71395 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-71395?
CVE-2025-71395 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2025-71395?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71395, 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
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71395
Is Your Infrastructure Affected by CVE-2025-71395?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.