| CVE-2025-1094US | — | 90.0% (100th) | Exploit | ✓16.7 | 2025-02-13 | 5 versions |
| CVE-2026-2005US | — | 1.37% (72nd) | Exploit | ✓14.21 | 2026-02-12 | 5 versions |
| CVE-2025-8714US | — | 0.76% (55th) | Exploit | ✓14.19 | 2025-08-14 | 5 versions |
| CVE-2026-14669US | — | 0.66% (52nd) | Exploit | ✓18.5 | 2026-08-13 | 5 versions |
| CVE-2026-6471US | —OT elevated | 0.53% (45th) | Exploit | ✓17.11 | 2026-08-13 | 5 versions |
| CVE-2026-14662US | — | 0.46% (40th) | Exploit | ✓18.5 | 2026-08-13 | 5 versions |
| CVE-2026-6475US | — | 0.41% (35th) | Exploit | ✓14.23 | 2026-05-14 | 5 versions |
| CVE-2020-25695US | high8.8 | 46.4% (99th) | — | ✗no fix | 2020-11-16 | ≤ All PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24 |
| CVE-2022-1552US | high8.8OT elevated | 17.0% (97th) | — | ✗no fix | 2022-08-31 | ≤ Fixed in postgresql 14.3, postgresql 13.7, postgresql 12.11, postgresql 11.16, postgresql 10.21. |
| CVE-2024-10979US | high8.8 | 4.39% (91st) | — | ✓17.1 | 2024-11-14 | 6 versions |
| CVE-2020-25696US | high7.5 | 2.70% (86th) | — | ✗no fix | 2020-11-23 | ≤ All PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24 |
| CVE-2020-14349US | high7.1 | 2.23% (83rd) | — | ✗no fix | 2020-08-24 | ≤ PostgreSQL versions before 12.4, before 11.9 and before 10.14 |
| CVE-2022-2625US | high8.0 | 2.04% (81st) | — | ✗no fix | 2022-08-18 | ≤ postgresql 14.5, postgresql 13.8, postgresql 12.12, postgresql 11.17, postgresql 10.22 |
| CVE-2021-32027US | high8.8 | 1.99% (81st) | — | ✗no fix | 2021-06-01 | ≤ postgresql 13.3, postgresql 12.7, postgresql 11.12, postgresql 10.17, postgresql 9.6.22 |
| CVE-2021-23214US | high8.1OT elevated | 1.90% (80th) | — | ✗no fix | 2022-03-04 | ≤ Affects v9.6 to v14 |
| CVE-2024-0985US | high8.0 | 1.81% (79th) | — | ✓13.14 | 2024-02-08 | 6 versions |
| CVE-2020-25694US | high8.1OT elevated | 1.59% (76th) | — | ✗no fix | 2020-11-16 | ≤ All PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24 |
| CVE-2024-7348US | high7.5 | 1.57% (75th) | — | ✓13.16 | 2024-08-08 | 5 versions |
| CVE-2021-32028US | medium6.5 | 1.56% (75th) | — | ✗no fix | 2021-10-11 | ≤ postgresql 13.3, postgresql 12.7, postgresql 11.12, postgresql 10.17, postgresql 9.6.22 |
| CVE-2021-32029US | medium6.5 | 1.50% (74th) | — | ✗no fix | 2021-10-08 | ≤ postgresql 13.3, postgresql 12.7, postgresql 11.12 |
| CVE-2021-23222US | medium5.9 | 1.50% (74th) | — | ✗no fix | 2022-03-02 | ≤ Affects v9.6 to v14 |
| CVE-2021-20229US | medium4.3OT elevated | 1.47% (74th) | — | ✗no fix | 2021-02-23 | ≤ postgresql 13.2, postgresql 12.6, postgresql 11.11, postgresql 10.16, postgresql 9.6.21, postgresql 9.5.25 |
| CVE-2021-3677US | medium6.5 | 1.44% (73rd) | — | ✗no fix | 2022-03-02 | ≤ Fixedin v13.4, v12.8, v11.13 |
| CVE-2026-2004US | — | 1.34% (71st) | — | ✓14.21 | 2026-02-12 | 5 versions |
| CVE-2023-2454US | high7.2OT elevated | 1.20% (68th) | — | ✗no fix | 2023-06-09 | ≤ PostgreSQL 15.3, PostgreSQL 14.8, PostgreSQL 13.11, PostgreSQL 12.15, PostgreSQL 11.20 |
| CVE-2021-3393US | medium4.3 | 1.19% (68th) | — | ✗no fix | 2021-04-01 | ≤ postgresql 13.2, postgresql 12.6, postgresql 11.11 |
| CVE-2026-2006US | — | 1.16% (67th) | — | ✓15.16 | 2026-02-12 | 5 versions |
| CVE-2026-6473US | — | 1.01% (63rd) | — | ✓15.18 | 2026-05-14 | 5 versions |
| CVE-2024-10976US | medium5.4 | 0.77% (55th) | — | ✓15.9 | 2024-11-14 | 6 versions |
| CVE-2025-4207US | — | 0.76% (55th) | — | ✓13.21 | 2025-05-08 | 5 versions |
| CVE-2024-4317US | medium4.3OT elevated | 0.73% (54th) | — | ✓15.7 | 2024-05-14 | 3 versions |
| CVE-2023-2455US | medium5.4OT elevated | 0.70% (53rd) | — | ✗no fix | 2023-06-09 | ≤ PostgreSQL 15.3, PostgreSQL 14.8, PostgreSQL 13.11, PostgreSQL 12.15, PostgreSQL 11.20 |
| CVE-2024-10978US | medium4.2 | 0.69% (53rd) | — | ✓12.21 | 2024-11-14 | 6 versions |
| CVE-2026-16239US | — | 0.68% (52nd) | — | ✓17.11 | 2026-08-13 | 5 versions |
| CVE-2022-41862US | low3.7OT elevated | 0.62% (50th) | — | ✗no fix | 2023-03-03 | ≤ postgresql 5.2, postgresql 14.7, postgresql 13.10, postgresql 12.14, postgresql 11.19 |
| CVE-2026-15742US | — | 0.60% (48th) | — | ✓14.24 | 2026-08-13 | 5 versions |
| CVE-2026-6479US | — | 0.60% (48th) | — | ✓18.4 | 2026-05-14 | 5 versions |
| CVE-2026-6478US | — | 0.56% (46th) | — | ✓15.18 | 2026-05-14 | 5 versions |
| CVE-2026-2007US | — | 0.55% (46th) | — | ✓18.2 | 2026-02-12 | 18 → 18.2 |
| CVE-2020-14350US | high7.3 | 0.53% (45th) | — | ✗no fix | 2020-08-24 | ≤ PostgreSQL versions before 12.4, before 11.9, before 10.14, before 9.6.19, and before 9.5.23 |
| CVE-2020-10733US | high7.3 | 0.53% (45th) | — | ✗no fix | 2020-09-16 | ≤ 9.5, 9.6, 10, 11, 12 |
| CVE-2026-6477US | — | 0.45% (39th) | — | ✓14.23 | 2026-05-14 | 5 versions |
| CVE-2019-10128US | high7.8 | 0.45% (39th) | — | ✗no fix | 2021-03-19 | ≤ 11.x prior to 11.3 |
| CVE-2026-14676US | — | 0.44% (38th) | — | ✓18.5 | 2026-08-13 | 18 → 18.5 |
| CVE-2026-14670US | — | 0.44% (38th) | — | ✓14.24 | 2026-08-13 | 5 versions |
| CVE-2026-14664US | — | 0.44% (38th) | — | ✓17.11 | 2026-08-13 | 5 versions |
| CVE-2026-15741US | — | 0.43% (38th) | — | ✓15.19 | 2026-08-13 | 5 versions |
| CVE-2026-19385US | — | 0.43% (37th) | — | ✓14.24 | 2026-08-13 | 5 versions |
| CVE-2025-8715US | — | 0.43% (37th) | — | ✓13.22 | 2025-08-14 | 5 versions |
| CVE-2026-14680US | — | 0.42% (36th) | — | ✓15.19 | 2026-08-13 | 5 versions |