Memory Corruption

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

1. zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.CVE-2018-25032Zlib · CVSS 7.5 · 52% likely

   CWE-787

2. zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetH…CVE-2022-37434Zlib · CVSS 9.8 · 19% likely

   CWE-120

3. The decompression algorithm in zlib 1.1.3 and earlier, as used in many different utilities and packages, causes inflateEnd to release certain memory more than once (a "double free…CVE-2002-0059Zlib · 9.7% likely

   CWE-415

4. MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip…CVE-2023-45853Zlib · CVSS 8.8 · 3.4% likely

   CWE-190

5. zlib 1.2.11 through 1.3.2 Heap Buffer Overflow via Stale gzwrite Pointer After Failed WriteCVE-2026-85091zlib · CVSS 7.4 · 0.5% likely

   CWE-787

6. zlib <= 1.3.1.2 untgz Global Buffer Overflow in TGZfname()CVE-2026-22184zlib software · CVSS 8.6 · 0.4% likely

   CWE-787

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.