CVE-2023-0921

CRITICALNVD 4.39.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 84% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 4.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, ghsa, nvd
Elevated
9.0EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • 32 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • High exploitation likelihood — EPSS 84%
CISA-KEV: Not listedEPSS PROB: 84%CVSS: 4.3Exploit: Elevated riskExposed services: 32

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

A lack of length validation in GitLab CE/EE affecting all versions from 8.3 before 15.10.8, 15.11 before 15.11.7, and 16.0 before 16.0.2 allows an authenticated attacker to create a large Issue description via GraphQL which, when repeatedly requested, saturates CPU usage.

Internet exposure · derived from Shodan data

32 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2023-0921, in our KEV-Exposure radar’s Shodan-derived sample.

across 8 countries (United States, China, Singapore, Germany, Thailand)top: gitlab
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v3
4.3
EG Score
9.0CRITICALhigh confidence
EG Risk
74
EG Risk 74/100CISA SSVC

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
Severity90% × 45%
Exploitation84% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
84%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 6, 2023

Last Modified

May 5, 2025

References (6)

Vendor Advisories for CVE-2023-0921(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-0921?
CVE-2023-0921 is a critical vulnerability published on June 6, 2023. A lack of length validation in GitLab CE/EE affecting all versions from 8.3 before 15.10.8, 15.11 before 15.11.7, and 16.0 before 16.0.2 allows an authenticated attacker to create a large Issue description via GraphQL which, when repeatedly requested, saturates CPU usage.
When was CVE-2023-0921 disclosed?
CVE-2023-0921 was first published on June 6, 2023, with the most recent update on May 5, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-0921 actively exploited?
CVE-2023-0921 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 84% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-0921?
CVE-2023-0921 has a CVSS v3 base score of 4.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2023-0921?
No fix for CVE-2023-0921 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2023-0921 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-0921

Explore →

Is Your Infrastructure Affected by CVE-2023-0921?

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

Book a Demo →Browse All CVEs