Memory Corruption

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

1. The XML libraries for Python 3.4, 3.3, 3.2, 3.1, 2.7, and 2.6, as used in OpenStack Keystone Essex, Folsom, and Grizzly; Compute (Nova) Essex and Folsom; Cinder Folsom; Django; an…CVE-2013-1664Openstack · 4.8% likely

   CWE-119

2. The template-validate command in OpenStack Orchestration API (Heat) before 2015.1.3 (kilo) and 5.0.x before 5.0.1 (liberty) allows remote authenticated users to cause a denial of…CVE-2015-5295Openstack · 2.9% likely

   CWE-119

3. The security group extension in OpenStack Compute (Nova) Grizzly 2013.1.3, Havana before havana-3, and earlier allows remote attackers to cause a denial of service (resource consu…CVE-2013-4179Openstack · 2.7% likely

   CWE-119

4. OpenStack Compute (Nova) Folsom, Grizzly, and earlier, when using Apache Qpid for the RPC backend, does not properly handle errors that occur during messaging, which allows remote…CVE-2013-4261Openstack · 1.7% likely

   CWE-119

5. OpenStack Swift before 1.9.1 in Folsom, Grizzly, and Havana allows authenticated users to cause a denial of service ("superfluous" tombstone consumption and Swift cluster slowdown…CVE-2013-4155Openstack · 1.7% likely

   CWE-119

6. In OpenStack Keystone before 29.0.3, any authenticated user holding role:reader on any project can list every project-scoped role assignment under any domain by passing a domain I…CVE-2026-80183OpenStack · CVSS 7.1 · 0.4% likely

   CWE-843

7. In OpenStack Keystone before 28.0.1, the LDAP identity backend does not convert the user enabled attribute to a boolean when the user_enabled_invert configuration option is False…CVE-2026-40683OpenStack · CVSS 7.7 · 0.3% likely

   CWE-843

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.