Return of Stack Variable Address

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

1. An exploitable return of stack variable address vulnerability exists in the JavaScript implementation of Nitro Pro PDF. A specially crafted document can cause a stack variable to…CVE-2021-21798Gonitro · CVSS 8.8 · 21% likely

   Gonitro

2. An out-of-bounds write vulnerability exists in the OpenImageIO::add_exif_item_to_spec functionality of OpenImageIO Project OpenImageIO v2.4.4.2. Specially-crafted exif metadata ca…CVE-2022-41837OpenImageIO Project · CVSS 9.8 · 1.7% likely

   OpenImageIO Project

3. Libvirt: stack use-after-free in virnetclientioeventloop()CVE-2024-4418Redhat · CVSS 6.2 · 0.5% likely

   Red Hat

4. A stack-use-after-scope issue discovered in expand_mmac_params function in preproc.c in nasm before 2.15.04 allows remote attackers to cause a denial of service via crafted asm fi…CVE-2020-21686Nasm · 0.4% likely

   Nasm

5. A stack use-after-return flaw in SIG(0) handling code may enable ACL bypassCVE-2026-3591ISC · CVSS 5.4 · 0.4% likelycovered by CyberSIXT

   Isc

6. A stack-use-after-return issue exists in the Arduino_Core_STM32 library prior to version 1.7.0. The pwm_start() function allocates a TIM_HandleTypeDef structure on the stack and p…CVE-2026-26399CVSS 5.3 · 0.2% likely
7. iccDEV: DoS in CIccCLUT::Iterate() & CIccMBB::Describe()CVE-2026-34553InternationalColorConsortium · CVSS 4 · 0.2% likely

   InternationalColorConsortium

8. Return of Stack Variable Address in BusesCVE-2024-33045Qualcomm, Inc. · CVSS 8.4 · 0.1% likely

   Qualcomm, Inc.

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.