Postgresql · weakness class
Memory Corruption
47 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
Every one of the 47 is a mark on the map. Named now: 1 to 26, most at risk first.
- PostgreSQL before 9.1.20, 9.2.x before 9.2.15, 9.3.x before 9.3.11, 9.4.x before 9.4.6, and 9.5.x before 9.5.1 allows remote attackers to cause a denial of service (infinite loop…
- Multiple stack-based buffer overflows in PostgreSQL before 8.4.20, 9.0.x before 9.0.16, 9.1.x before 9.1.12, 9.2.x before 9.2.7, and 9.3.x before 9.3.3 allow remote authenticated…
- PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before 9.3.14, 9.4.x before 9.4.9, and 9.5.x before 9.5.4 allow remote authenticated users to cause a denial of service (NULL…
- Multiple buffer overflows in PostgreSQL before 8.4.20, 9.0.x before 9.0.16, 9.1.x before 9.1.12, 9.2.x before 9.2.7, and 9.3.x before 9.3.3 allow remote authenticated users to hav…
- Multiple stack-based buffer overflows in json parsing in PostgreSQL before 9.3.x before 9.3.10 and 9.4.x before 9.4.5 allow attackers to cause a denial of service (server crash) v…
- PostgreSQL versions 10.x before 10.9 and versions 11.x before 11.4 are vulnerable to a stack-based buffer overflow. Any authenticated user can overflow a stack-based buffer by cha…
- Multiple buffer overflows in gram.y for PostgreSQL 8.0.1 and earlier may allow attackers to execute arbitrary code via (1) a large number of variables in a SQL statement being han…
- Unchecked Class Instantiation when providing Plugin Classes
- Buffer overflows in (1) circle_poly, (2) path_encode and (3) path_add (also incorrectly identified as path_addr) for PostgreSQL 7.2.3 and earlier allow attackers to cause a denial…
- A flaw was found in postgresql in versions before 13.3, before 12.7, before 11.12, before 10.17 and before 9.6.22. While modifying certain SQL array values, missing bounds checks…
- A vulnerability was found in postgresql versions 11.x prior to 11.3. Using a purpose-crafted insert to a partitioned table, an attacker can read arbitrary bytes of server memory.…
- PostgreSQL pgcrypto heap buffer overflow executes arbitrary code
- PostgreSQL missing validation of multibyte character length executes arbitrary code
- Postgresql, versions 11.x before 11.5, is vulnerable to a memory disclosure in cross-type comparison for hashed subplan.
- PostgreSQL server undersizes allocations, via integer wraparound
- PostgreSQL type confusion in cursor CLOSE + DECLARE executes arbitrary code
- PostgreSQL to_char heap buffer overflow executes arbitrary code
- PostgreSQL fuzzystrmatch writes effectively-arbitrary addresses, via integer wraparound
- PostgreSQL pg_trgm heap buffer overflow writes pattern onto server memory
- PostgreSQL tsvector and tsquery undersize allocations, via integer wraparound
- PostgreSQL libpq lo_* functions let server superuser overwrite client stack memory
- PostgreSQL pg_stat_statements heap buffer overflow executes arbitrary code
- PostgreSQL plperl tied object heap buffer overflow executes arbitrary code
- PostgreSQL regexp heap buffer overflow executes arbitrary code
- PostgreSQL pg_dump heap buffer overflow executes arbitrary code
- PostgreSQL type confusion via "internal" arguments
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.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.