Exploitation timeline
Threadlinqs has recorded 7 pgadmin.org CVEs published between and . The busiest month was 2026-06 (7 new CVEs). None of them is listed in CISA KEV yet.
Most exploited vulnerabilities
Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 7 of 7 tracked pgadmin.org CVEs.
- CVE-2026-12046critical 9EPSS 1%
- CVE-2026-12045critical 9EPSS 0.7%
- CVE-2026-12050medium 4.3EPSS 0.4%
- CVE-2026-12049medium 4.3EPSS 0.4%
- CVE-2026-12048critical 9.3EPSS 0.3%
- CVE-2026-12047low 3.5EPSS 0.2%
- CVE-2026-12044high 8.8
Products affected
Threadlinqs normalises CPE and CNA product records across all 7 CVEs; 1 distinct pgadmin.org product is affected. The most frequently affected:
- pgAdmin 4 7 CVEs
Threat activity
1 tracked threat campaign reference pgadmin.org products or exploit pgadmin.org CVEs:
How to prioritise pgadmin.org patching
This order follows the data Threadlinqs holds for pgadmin.org, not a generic severity checklist:
- No pgadmin.org CVE is in CISA KEV yet, so rank by exploit probability instead.
- Outside KEV, the highest EPSS scores are CVE-2026-12046 (1%), CVE-2026-12045 (0.7%), CVE-2026-12050 (0.4%).
- 3 CVEs score Critical and 1 High on CVSS v3 (maximum 9.3, average 6.9); sequence these after KEV and high-EPSS items.
- 3 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.
About this data
Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-11-19 and refresh daily.