CVE-2024-58368

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-18. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

SurrealDB versions before 1.1.0 fail to properly parse the ID, DB, and NS headers in HTTP REST API requests containing special characters. Unauthenticated attackers can send crafted HTTP requests with malformed header values to trigger an uncaught exception that crashes the server.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

July 18, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jul 18, 2026
Patch available. Sources: github.
generic

SurrealDB before 1.1.0 Denial of Service via HTTP Headers | Advisories | VulnCheck

https://www.vulncheck.com/advisories/surrealdb-before-denial-of-service-via-http-headers
github Patch Available

Uncaught Exception Processing HTTP Headers · Advisory · surrealdb/surrealdb · GitHub

https://github.com/surrealdb/surrealdb/security/advisories/GHSA-m24x-r6q3-2vp9

Vendor Advisories for CVE-2024-58368(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)
PackageVulnerable rangeFixed inDependents
surrealdb—1.1.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 23× 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-07-27 09:11 UTCGHSA enrichment
  2. 2026-07-26 22:14 UTCEG score recompute
  3. 2026-07-26 22:14 UTCGHSA enrichment
  4. 2026-07-26 14:53 UTCEPSS rescore
  5. 2026-07-26 11:17 UTCEG score recompute
  6. 2026-07-26 11:16 UTCGHSA enrichment
  7. 2026-07-25 14:17 UTCEPSS rescore
  8. 2026-07-25 14:17 UTCEPSS rescore
  9. 2026-07-24 14:16 UTCEPSS rescore
  10. 2026-07-23 14:17 UTCEPSS rescore
  11. 2026-07-23 14:17 UTCEPSS rescore
  12. 2026-07-23 02:45 UTCEG score recompute
  13. 2026-07-22 23:58 UTCEG score recompute
  14. 2026-07-22 23:58 UTCGHSA enrichment
  15. 2026-07-22 14:07 UTCEPSS rescore
  16. 2026-07-21 15:23 UTCEPSS rescore
  17. 2026-07-20 17:07 UTCEPSS rescore
  18. 2026-07-19 14:30 UTCEPSS rescore
  19. 2026-07-19 14:30 UTCEPSS rescore
  20. 2026-07-18 16:06 UTCEG score recompute
  21. 2026-07-18 16:06 UTCGHSA enrichment
  22. 2026-07-18 13:40 UTCEG score recompute
  23. 2026-07-18 13:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2024-58368?
CVE-2024-58368 is a high vulnerability published on July 18, 2026. SurrealDB versions before 1.1.0 fail to properly parse the ID, DB, and NS headers in HTTP REST API requests containing special characters. Unauthenticated attackers can send crafted HTTP requests with malformed header values to trigger an uncaught exception that crashes the server.
When was CVE-2024-58368 disclosed?
CVE-2024-58368 was first published in the National Vulnerability Database on July 18, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-58368 actively exploited?
CVE-2024-58368 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 69.8% of all scored CVEs.
What is the CVSS score of CVE-2024-58368?
CVE-2024-58368 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-58368?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-58368, 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-2024-58368

Explore →

Is Your Infrastructure Affected by CVE-2024-58368?

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

Start Free Scan →Browse All CVEs