Memory Corruption

Every one of the 7 is a mark on the map. Named now: 1 to 7, most at risk first.

1. GitLab CE/EE < 19.2.8 / 19.3.5 / 19.4.2 - Unauthenticated RCE via Onigmo Integer OverflowCVE-2026-97229GitLab · CVSS 10 · 69% likelycovered by CyberSIXT

   CWE-19014 articles

2. Integer Overflow or Wraparound in GitLabCVE-2026-110264GitLab · CVSS 10 · 1.3% likelycovered by CyberSIXT

   CWE-1904 articles

3. A denial of service vulnerability when rendering RDoc files in GitLab CE/EE versions 10 to 14.7.7, 14.8.0 to 14.8.5, and 14.9.0 to 14.9.2 allows an attacker to crash the GitLab we…CVE-2022-1185GitLab · CVSS 6.5 · 1.3% likely

   CWE-787

4. An issue has been discovered in GitLab affecting all versions prior to 13.2.10, 13.3.7 and 13.4.2. Insufficient permission check allows attacker with developer role to perform var…CVE-2020-13341GitLab · CVSS 4.9 · 1.2% likely

   CWE-843

5. Integer Overflow or Wraparound in GitLabCVE-2026-93577GitLab · CVSS 9.9 · 0.6% likelycovered by CyberSIXT

   CWE-1902 articles

6. In Gitlab EE/CE before 15.6.1, 15.5.5 and 15.4.6 using a branch with a hexadecimal name could override an existing hash.CVE-2022-4205GitLab · CVSS 6.3 · 0.6% likely

   CWE-843

7. Double Free in GitLabCVE-2026-89078GitLab · CVSS 9.9 · 0.5% likelycovered by CyberSIXT

   CWE-4152 articles

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.