CVE-2023-32758

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2023-05-15. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

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

giturlparse (aka git-url-parse) through 1.2.2, as used in Semgrep 1.5.2 through 1.24.1, is vulnerable to ReDoS (Regular Expression Denial of Service) if parsing untrusted URLs. This might be relevant if Semgrep is analyzing an untrusted package (for example, to check whether it accesses any Git repository at an http:// URL), and that package's author placed a ReDoS attack payload in a URL used by the package.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
59.9%
KEV
Not listed

Published

May 15, 2023

Last Modified

January 23, 2025

References (10)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipgit-url-parse—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
git-url-parse1.0.0 ... 1.2.2 (7 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 51× 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-16 17:01 UTCEPSS rescore
  2. 2026-07-15 20:23 UTCOSV refresh
  3. 2026-07-15 16:56 UTCEPSS rescore
  4. 2026-07-15 16:56 UTCEPSS rescore
  5. 2026-07-15 01:58 UTCEPSS rescore
  6. 2026-07-15 01:58 UTCEPSS rescore
  7. 2026-07-13 22:28 UTCEPSS rescore
  8. 2026-07-13 22:28 UTCEPSS rescore
  9. 2026-07-13 06:11 UTCEPSS rescore
  10. 2026-07-13 06:11 UTCEPSS rescore
  11. 2026-07-12 05:45 UTCEPSS rescore
  12. 2026-07-11 08:26 UTCEPSS rescore
  13. 2026-07-11 08:25 UTCEPSS rescore
  14. 2026-07-09 19:08 UTCEPSS rescore
  15. 2026-07-09 19:08 UTCEPSS rescore
  16. 2026-07-08 15:13 UTCEPSS rescore
  17. 2026-07-07 13:44 UTCEPSS rescore
  18. 2026-07-06 16:26 UTCEPSS rescore
  19. 2026-07-06 16:26 UTCEPSS rescore
  20. 2026-07-06 02:21 UTCEPSS rescore
  21. 2026-07-05 02:29 UTCEPSS rescore
  22. 2026-07-04 06:29 UTCEPSS rescore
  23. 2026-07-02 16:59 UTCEPSS rescore
  24. 2026-07-01 15:04 UTCEPSS rescore
  25. 2026-06-30 23:21 UTCEPSS rescore
Show 74 more
  1. 2026-06-30 23:21 UTCEPSS rescore
  2. 2026-06-28 14:06 UTCEPSS rescore
  3. 2026-06-28 14:06 UTCEPSS rescore
  4. 2026-06-28 04:55 UTCEPSS rescore
  5. 2026-06-28 04:55 UTCEPSS rescore
  6. 2026-06-27 21:04 UTCOSV refresh
  7. 2026-06-27 03:07 UTCEPSS rescore
  8. 2026-06-27 03:07 UTCEPSS rescore
  9. 2026-06-25 13:48 UTCEPSS rescore
  10. 2026-06-25 13:48 UTCEPSS rescore
  11. 2026-06-24 14:04 UTCEPSS rescore
  12. 2026-06-24 14:03 UTCEPSS rescore
  13. 2026-06-23 21:31 UTCEPSS rescore
  14. 2026-06-23 21:31 UTCEPSS rescore
  15. 2026-06-22 14:24 UTCEPSS rescore
  16. 2026-06-22 14:24 UTCEPSS rescore
  17. 2026-06-21 14:55 UTCEPSS rescore
  18. 2026-06-21 14:55 UTCEPSS rescore
  19. 2026-06-21 01:58 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-19 19:24 UTCEPSS rescore
  22. 2026-06-19 19:24 UTCEPSS rescore
  23. 2026-06-18 17:51 UTCEPSS rescore
  24. 2026-06-18 17:51 UTCEPSS rescore
  25. 2026-06-17 17:51 UTCEPSS rescore
  26. 2026-06-17 17:51 UTCEPSS rescore
  27. 2026-06-16 17:51 UTCEPSS rescore
  28. 2026-06-16 17:51 UTCEPSS rescore
  29. 2026-06-15 17:47 UTCEPSS rescore
  30. 2026-06-14 23:16 UTCEPSS rescore
  31. 2026-06-13 22:59 UTCEPSS rescore
  32. 2026-06-13 22:59 UTCEPSS rescore
  33. 2026-06-12 23:10 UTCEPSS rescore
  34. 2026-06-12 23:10 UTCEPSS rescore
  35. 2026-06-11 13:59 UTCEPSS rescore
  36. 2026-06-11 13:59 UTCEPSS rescore
  37. 2026-06-10 22:17 UTCEPSS rescore
  38. 2026-06-10 13:21 UTCEPSS rescore
  39. 2026-06-10 07:47 UTCOSV refresh
  40. 2026-06-08 14:16 UTCEPSS rescore
  41. 2026-06-08 14:15 UTCEPSS rescore
  42. 2026-06-07 15:23 UTCEPSS rescore
  43. 2026-06-07 15:23 UTCEPSS rescore
  44. 2026-06-06 13:46 UTCEPSS rescore
  45. 2026-06-06 13:46 UTCEPSS rescore
  46. 2026-06-05 22:46 UTCEPSS rescore
  47. 2026-06-05 22:46 UTCEPSS rescore
  48. 2026-06-05 06:09 UTCEPSS rescore
  49. 2026-06-05 06:09 UTCEPSS rescore
  50. 2026-06-04 13:11 UTCEPSS rescore
  51. 2026-06-04 13:11 UTCEPSS rescore
  52. 2026-06-02 20:12 UTCEPSS rescore
  53. 2026-06-02 20:12 UTCEPSS rescore
  54. 2026-06-02 20:12 UTCEPSS rescore
  55. 2026-06-01 13:51 UTCEPSS rescore
  56. 2026-06-01 13:51 UTCEPSS rescore
  57. 2026-05-31 22:30 UTCEPSS rescore
  58. 2026-05-31 22:29 UTCEPSS rescore
  59. 2026-05-31 22:29 UTCEPSS rescore
  60. 2026-05-31 00:15 UTCEPSS rescore
  61. 2026-05-31 00:15 UTCEPSS rescore
  62. 2026-05-29 13:43 UTCEPSS rescore
  63. 2026-05-29 13:43 UTCEPSS rescore
  64. 2026-05-28 13:43 UTCEPSS rescore
  65. 2026-05-28 13:43 UTCEPSS rescore
  66. 2026-05-27 13:39 UTCEPSS rescore
  67. 2026-05-26 13:43 UTCEPSS rescore
  68. 2026-05-26 13:43 UTCEPSS rescore
  69. 2026-05-26 07:18 UTCEPSS rescore
  70. 2026-05-26 07:18 UTCEPSS rescore
  71. 2026-05-26 07:18 UTCEPSS rescore
  72. 2026-05-25 01:10 UTCEG score recompute
  73. 2026-05-25 01:10 UTCGHSA enrichment
  74. 2026-05-24 16:52 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-32758?
CVE-2023-32758 is a high vulnerability published on May 15, 2023. giturlparse (aka git-url-parse) through 1.2.2, as used in Semgrep 1.5.2 through 1.24.1, is vulnerable to ReDoS (Regular Expression Denial of Service) if parsing untrusted URLs. This might be relevant if Semgrep is analyzing an untrusted package (for example, to check whether it accesses any Git…
When was CVE-2023-32758 disclosed?
CVE-2023-32758 was first published in the National Vulnerability Database on May 15, 2023, with the most recent update on January 23, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-32758 actively exploited?
CVE-2023-32758 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-32758?
CVE-2023-32758 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-32758?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-32758, 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-2023-32758

Explore →

Is Your Infrastructure Affected by CVE-2023-32758?

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

Start Free Scan →Browse All CVEs