CVE-2023-6840

MEDIUMNVD 6.76.7—
EchelonGraph scoreMEDIUM confidence

Score 6.7 from GitHub Security Advisory published 2024-02-08. NVD baseline CVSS 6.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, nvd
Elevated
6.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.7Exploit: NoneExposed: 0

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

An issue has been discovered in GitLab EE affecting all versions from 16.4 prior to 16.6.7, 16.7 prior to 16.7.5, and 16.8 prior to 16.8.2 which allows a maintainer to change the name of a protected branch that bypasses the security policy added to block MR.

CVSS v3
6.7
EG Score
6.7(medium)
EPSS
42.7%
KEV
Not listed

Published

February 7, 2024

Last Modified

November 21, 2024

References (4)

Vendor Advisories for CVE-2023-6840(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 9× in last 7d / 46× 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-06 16:26 UTCEPSS rescore
  2. 2026-07-06 16:26 UTCEPSS rescore
  3. 2026-07-06 02:22 UTCEPSS rescore
  4. 2026-07-06 02:22 UTCEPSS rescore
  5. 2026-07-05 02:29 UTCEPSS rescore
  6. 2026-07-04 06:29 UTCEPSS rescore
  7. 2026-07-01 15:05 UTCEPSS rescore
  8. 2026-06-30 23:21 UTCEPSS rescore
  9. 2026-06-30 23:21 UTCEPSS rescore
  10. 2026-06-29 14:05 UTCEPSS rescore
  11. 2026-06-28 14:06 UTCEPSS rescore
  12. 2026-06-28 14:06 UTCEPSS rescore
  13. 2026-06-28 04:55 UTCEPSS rescore
  14. 2026-06-27 03:07 UTCEPSS rescore
  15. 2026-06-25 13:48 UTCEPSS rescore
  16. 2026-06-25 13:48 UTCEPSS rescore
  17. 2026-06-24 19:01 UTCOSV refresh
  18. 2026-06-24 14:04 UTCEPSS rescore
  19. 2026-06-24 14:04 UTCEPSS rescore
  20. 2026-06-23 21:31 UTCEPSS rescore
  21. 2026-06-23 21:31 UTCEPSS rescore
  22. 2026-06-22 14:24 UTCEPSS rescore
  23. 2026-06-22 14:24 UTCEPSS rescore
  24. 2026-06-21 14:55 UTCEPSS rescore
  25. 2026-06-21 14:55 UTCEPSS rescore
Show 41 more
  1. 2026-06-21 01:58 UTCEPSS rescore
  2. 2026-06-21 01:58 UTCEPSS rescore
  3. 2026-06-19 19:24 UTCEPSS rescore
  4. 2026-06-19 19:24 UTCEPSS rescore
  5. 2026-06-18 17:51 UTCEPSS rescore
  6. 2026-06-17 17:51 UTCEPSS rescore
  7. 2026-06-16 17:51 UTCEPSS rescore
  8. 2026-06-16 17:51 UTCEPSS rescore
  9. 2026-06-15 17:47 UTCEPSS rescore
  10. 2026-06-14 23:16 UTCEPSS rescore
  11. 2026-06-13 22:59 UTCEPSS rescore
  12. 2026-06-13 22:59 UTCEPSS rescore
  13. 2026-06-12 23:11 UTCEPSS rescore
  14. 2026-06-11 13:59 UTCEPSS rescore
  15. 2026-06-10 22:17 UTCEPSS rescore
  16. 2026-06-10 13:21 UTCEPSS rescore
  17. 2026-06-08 14:16 UTCEPSS rescore
  18. 2026-06-08 14:16 UTCEPSS rescore
  19. 2026-06-07 20:16 UTCOSV refresh
  20. 2026-06-07 15:24 UTCEPSS rescore
  21. 2026-06-07 15:24 UTCEPSS rescore
  22. 2026-06-06 13:46 UTCEPSS rescore
  23. 2026-06-06 13:46 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-06-02 20:12 UTCEPSS rescore
  27. 2026-06-02 20:12 UTCEPSS rescore
  28. 2026-06-01 13:51 UTCEPSS rescore
  29. 2026-05-31 00:15 UTCEPSS rescore
  30. 2026-05-31 00:15 UTCEPSS rescore
  31. 2026-05-29 13:43 UTCEPSS rescore
  32. 2026-05-28 13:44 UTCEPSS rescore
  33. 2026-05-28 13:44 UTCEPSS rescore
  34. 2026-05-27 13:40 UTCEPSS rescore
  35. 2026-05-27 13:39 UTCEPSS rescore
  36. 2026-05-26 13:43 UTCEPSS rescore
  37. 2026-05-26 13:43 UTCEPSS rescore
  38. 2026-05-26 07:18 UTCEPSS rescore
  39. 2026-05-26 07:18 UTCEPSS rescore
  40. 2026-05-23 10:13 UTCEG score recompute
  41. 2026-05-23 10:13 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-6840?
CVE-2023-6840 is a medium vulnerability published on February 7, 2024. An issue has been discovered in GitLab EE affecting all versions from 16.4 prior to 16.6.7, 16.7 prior to 16.7.5, and 16.8 prior to 16.8.2 which allows a maintainer to change the name of a protected branch that bypasses the security policy added to block MR.
When was CVE-2023-6840 disclosed?
CVE-2023-6840 was first published in the National Vulnerability Database on February 7, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-6840 actively exploited?
CVE-2023-6840 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-6840?
CVE-2023-6840 has a CVSS v3 base score of 6.7 (NVD).
How do I remediate CVE-2023-6840?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-6840, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2023-6840?

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

Start Free Scan →Browse All CVEs