SurrealDB versions before 2.0.4 fail to properly enforce field permissions during SELECT, UPDATE, and DELETE operations, allowing authorized users to access unauthorized field values through various query techniques. Attackers can exploit SELECT VALUE operations, field aliasing, function arguments, WHERE clause filtering, RETURN BEFORE clauses, and SET clause references to leak protected field contents despite lacking SELECT permissions.
CVE-2024-58367
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).
- High severity, but no confirmed exploitation yet
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
- 12.0%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 18, 2026SurrealDB before 2.0.4 Improper Authorization via SELECT Permissions | Advisories | VulnCheck
https://www.vulncheck.com/advisories/surrealdb-before-improper-authorization-via-select-permissionsImproper Authorization in Select Permissions · Advisory · surrealdb/surrealdb · GitHub
https://github.com/surrealdb/surrealdb/security/advisories/GHSA-9722-9j67-vjcrVendor Advisories for CVE-2024-58367(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.0.4 | — |
| surrealdb-core | — | 2.0.4 | — |
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: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:07 UTCEG score recompute
- 2026-07-18 16:06 UTCGHSA enrichment
- 2026-07-18 13:40 UTCEG score recompute
- 2026-07-18 13:39 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-285
Frequently asked(5)
What is CVE-2024-58367?
When was CVE-2024-58367 disclosed?
Is CVE-2024-58367 actively exploited?
What is the CVSS score of CVE-2024-58367?
How do I remediate CVE-2024-58367?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-58367
Is Your Infrastructure Affected by CVE-2024-58367?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.