Return of Wrong Status Code

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

1. Server-side Template Injection (SSTI) in gravCVE-2023-37897getgrav · CVSS 7.2 · 2.8% likely

   Getgrav

2. Libssh: invalid return code for chacha20 poly1305 with openssl backendCVE-2025-5987Red Hat · CVSS 8.1 · 1.7% likely

   Red Hat

3. Cloud Foundry GoRouter is vulnerable to cache poisoningCVE-2020-5401Cloud Foundry · CVSS 5.3 · 1.0% likely

   Cloud Foundry

4. Windows Hyper-V Remote Code Execution VulnerabilityCVE-2024-49117Microsoft · CVSS 8.8 · 1.0% likely

   Microsoft

5. In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds memory access can occur in the Python API (Python bindings) because of an incorrect return value. This occurs in x…CVE-2025-32414xmlsoft · CVSS 5.6 · 0.4% likely

   Xmlsoft

6. Sssd: sssd: access control bypass via premature ldap access rule evaluationCVE-2026-92821Red Hat · CVSS 6.8 · 0.3% likely

   Red Hat

7. In OpenSC pam_pkcs11 before 0.6.13, pam_sm_authenticate() wrongly returns PAM_IGNORE in many error situations (such as an error triggered by a smartcard before login), allowing au…CVE-2025-24531OpenSC project · CVSS 6.7 · 0.2% likely

   OpenSC

8. bpf: Fix linked reg delta tracking when src_reg == dst_regCVE-2026-53092Linux · CVSS 7.8 · 0.1% likely

   Linux

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.