Libical

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

1. The parser_get_next_char function in libical 0.47 and 1.0 allows remote attackers to cause a denial of service (out-of-bounds heap read) by crafting a string to the icalparser_par…CVE-2016-5826Libical Project · 3.2% likely

   CWE-125

2. The icaltime_from_string function in libical 0.47 and 1.0 allows remote attackers to cause a denial of service (out-of-bounds heap read) via a crafted string to the icalparser_par…CVE-2016-5827Libical Project · 3.1% likely

   CWE-125

3. libical allows remote attackers to cause a denial of service (use-after-free) and possibly read heap memory via a crafted ics file.CVE-2016-9584Libical Project · 2.3% likely

   CWE-416

4. libical 1.0 allows remote attackers to cause a denial of service (use-after-free) via a crafted ics file.CVE-2016-5824Libical Project · 2.2% likely

   CWE-416

5. The icalparser_parse_string function in libical 0.47 and 1.0 allows remote attackers to cause a denial of service (out-of-bounds heap read) via a crafted ics file.CVE-2016-5825Libical Project · 1.6% likely

   CWE-125

6. The icalproperty_new_clone function in libical 0.47 and 1.0 allows remote attackers to cause a denial of service (use-after-free) via a crafted ics file.CVE-2016-5823Libical Project · 1.0% likely

   CWE-416

7. libical through 4.0.6 Heap Out-of-Bounds Read via icalvalue_decode_ical_stringCVE-2026-111269libical · CVSS 6.1 · 0.2% 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.