SurrealDB before 2.1.4 silently fails to overwrite table definitions when the DEFINE TABLE ... OVERWRITE clause is used on tables defined with TYPE RELATION. Because table definitions include the PERMISSIONS clause, an attempt to tighten a table's permissions via OVERWRITE does not take effect, and the administrator may incorrectly believe the change was applied. As a result, a client authorized to run queries may continue to access data in that table that the updated (but unapplied) permissions were intended to restrict.
CVE-2024-58356
This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. 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).
- 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
- 2.3
- EG Score
- 2.3(medium)
- EG Risk
- 10(Track)EG Risk 10/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 computedSeverity23% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 18.2%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 21, 2026
References (2)
Vendor Advisories for CVE-2024-58356(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
crates.io(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| surrealdb | — | 2.1.4 | — |
| surrealdb-core | — | 2.1.4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× 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-23 02:45 UTCEG score recompute
- 2026-07-23 00:01 UTCEG score recompute
- 2026-07-23 00:00 UTCGHSA enrichment
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-20 17:07 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 16:08 UTCEG score recompute
- 2026-07-18 16:07 UTCGHSA enrichment
- 2026-07-18 13:41 UTCEG score recompute
- 2026-07-18 13:39 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-276
Frequently asked(5)
What is CVE-2024-58356?
When was CVE-2024-58356 disclosed?
Is CVE-2024-58356 actively exploited?
What is the CVSS score of CVE-2024-58356?
How do I remediate CVE-2024-58356?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-58356
Is Your Infrastructure Affected by CVE-2024-58356?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.