Memory Corruption

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

1. Integer overflow in table parsing extension leads to heap memory corruptionCVE-2022-24724github · CVSS 8.8 · 4.5% likely

   CWE-190

2. Use of Uninitialized Variable in trilogyCVE-2022-31026github · CVSS 5.9 · 1.1% likely

   CWE-908

3. GitHub MCP Server: Nil Pointer Dereference DoS in completion/complete HandlerCVE-2026-47427github · CVSS 7.5 · 0.8% likely

   CWE-476

4. cmark-gfm out-of-bounds read in validate_protocolCVE-2023-22485github · CVSS 5.3 · 0.7% likely

   CWE-125

5. Use-after-free vulnerability in GitHub Enterprise Server allowed remote code execution in the Git serviceCVE-2026-104608GitHub · CVSS 7.7 · 0.4% likely

   CWE-416

6. Out-of-bounds read vulnerability in GitHub Enterprise Server allowed disclosure of process memory in the Git serviceCVE-2026-118237GitHub · CVSS 5.3 · 0.3% likely

   CWE-125

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.