A vulnerability was found in PostgreSQL. This attack requires permission to create non-temporary objects in at least one schema, the ability to lure or wait for an administrator to create or update an affected extension in that schema, and the ability to lure or wait for a victim to use the object targeted in CREATE OR REPLACE or CREATE IF NOT EXISTS. Given all three prerequisites, this flaw allows an attacker to run arbitrary code as the victim role, which may be a superuser.
CVE-2022-2625
Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2022-08-19. NVD baseline CVSS 8.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.0
- EG Score
- 8.0HIGHmedium confidence
- EG Risk
- 41EG Risk 41/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity80% × 45%Exploitation2% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.9%
- EPSS %ILE
- 79th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 18, 2022
Last Modified
November 21, 2024
Advisory Details (3)
Auto-updated Sep 20, 2026PostgreSQL: PostgreSQL 14.5, 13.8, 12.12, 11.17, 10.22, and 15 Beta 3 Released!
https://www.postgresql.org/about/news/postgresql-145-138-1212-1117-1022-and-15-beta-3-released-2496/PostgreSQL: Multiple Vulnerabilities (GLSA 202211-04) — Gentoo security
https://security.gentoo.org/glsa/202211-042113825 – (CVE-2022-2625) CVE-2022-2625 postgresql: Extension scripts replace objects not belonging to the extension.
Affected: Red Hat Enterprise Linux 8
https://bugzilla.redhat.com/show_bug.cgi?id=2113825Vendor Advisories for CVE-2022-2625(6)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2023:7695Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql:13 security update
- RHSA-2023:7694Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql:12 security update
- RHSA-2023:7667Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql:12 security update
- RHSA-2023:7580Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql:13 security update
- RHSA-2023:7545Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql security update
- CVE-2022-2625Microsoft Security Response Center (MSRC)High
A vulnerability was found in PostgreSQL. This attack requires permission to create non-temporary objects in at least one schema the ability to lure or wait for an administrator to create or update an affected extension in that schema and the ability to lure or wait for a victim to use the object targeted in CREATE OR REPLACE or CREATE IF NOT EXISTS. Given all three prerequisites this flaw allows an attacker to run arbitrary code as the victim role which may be a superuser.
Patch Availability(11)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libecpg-compat3 (14.5-0ubuntu0.22.04.1) @ jammy | 2026-05-25 | ubuntu |
| redhat | postgresql:13-8040020231127154806.522a0ee4 | 2023-12-07 | redhat |
| redhat | postgresql:12-8040020231127153301.522a0ee4 | 2023-12-07 | redhat |
| redhat | postgresql:12-8020020231128165246.4cda2c84 | 2023-12-06 | redhat |
| redhat | postgresql:13-8060020231114115246.ad008a3a | 2023-11-29 | redhat |
| redhat | postgresql-0:13.13-1.el9_0 | 2023-11-28 | redhat |
| redhat | postgresql-0:13.10-1.el9_1 | 2023-04-11 | redhat |
| redhat | postgresql:13-8070020230227142544.bd1311ed | 2023-04-04 | redhat |
| redhat | rh-postgresql10-postgresql-0:10.23-1.el7 | 2023-01-12 | redhat |
| redhat | postgresql:10-8070020221124143148.bd1311ed | 2023-01-12 | redhat |
| redhat | postgresql:12-8060020221003080350.ad008a3a | 2022-10-25 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(14 across 10 ecosystems)
Alpine:v3.15(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql13 | — |
| — |
| postgresql14 | — |
| — |
Alpine:v3.16(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql13 | — |
| — |
| postgresql14 | — |
| — |
Alpine:v3.17(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql14 | — |
| — |
| postgresql15 | — |
| — |
Alpine:v3.18(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql14 | — |
| — |
| postgresql15 | — |
| — |
Alpine:v3.13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql | — |
| — |
Alpine:v3.14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql | — |
| — |
Alpine:v3.19(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql15 | — |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql15 | — |
| — |
Debian:10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql-11 | 11.10-0+deb10u1 ... 11.9-0+deb10u1 (16 versions) |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql-13 | 13.3-1 ... 13.7-0+deb11u1 (7 versions) |
| — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(6)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
- Red HatRHSA-2022:7128MODERATE2022-08-11
RHSA-2022:7128 — Moderate
- Red HatRHSA-2023:0113MODERATE2022-08-11
RHSA-2023:0113 — Moderate
- Red HatRHSA-2023:0160MODERATE2022-08-11
RHSA-2023:0160 — Moderate
- Red HatRHSA-2023:1576MODERATE2022-08-11
RHSA-2023:1576 — Moderate
- Red HatRHSA-2023:1693MODERATE2022-08-11
RHSA-2023:1693 — Moderate
- UbuntuUSN-5571-1MEDIUM
PostgreSQL vulnerability
Data Freshness Timeline
(refreshed 7× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 188 total refreshes for this CVE.
- 2026-10-09 20:04 UTCEPSS rescore
- 2026-10-08 16:40 UTCEPSS rescore
- 2026-10-07 23:45 UTCEPSS rescore
- 2026-10-06 15:14 UTCEPSS rescore
- 2026-10-05 17:40 UTCEPSS rescore
- 2026-10-04 23:19 UTCEPSS rescore
- 2026-10-03 14:23 UTCEPSS rescore
- 2026-10-02 16:23 UTCEPSS rescore
- 2026-09-30 15:52 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescore
- 2026-09-29 15:16 UTCEPSS rescore
- 2026-09-28 13:48 UTCEPSS rescore
- 2026-09-27 13:42 UTCEPSS rescore
- 2026-09-26 15:54 UTCEPSS rescore
- 2026-09-26 00:22 UTCEPSS rescore
- 2026-09-24 14:00 UTCEPSS rescore
- 2026-09-24 13:33 UTCOSV refresh
- 2026-09-23 13:45 UTCEPSS rescore
- 2026-09-22 14:44 UTCEPSS rescore
- 2026-09-20 20:13 UTCEPSS rescore
- 2026-09-19 15:38 UTCEPSS rescore
- 2026-09-18 19:24 UTCEPSS rescore
- 2026-09-16 14:05 UTCEPSS rescore
- 2026-09-15 03:06 UTCEPSS rescore
- 2026-09-12 14:57 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-11 14:49 UTCEPSS rescore
- 2026-09-11 09:33 UTCEPSS rescore
- 2026-09-08 21:57 UTCEPSS rescore
- 2026-09-07 15:58 UTCEPSS rescore
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 06:14 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescore
- 2026-09-04 13:57 UTCEPSS rescore
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-01 13:51 UTCEPSS rescore
- 2026-08-30 19:14 UTCEPSS rescore
- 2026-08-30 01:19 UTCEPSS rescore
- 2026-08-28 21:38 UTCEPSS rescore
- 2026-08-27 14:22 UTCEPSS rescore
- 2026-08-26 14:43 UTCEPSS rescore
- 2026-08-25 13:46 UTCEPSS rescore
- 2026-08-24 14:13 UTCEPSS rescore
- 2026-08-23 00:16 UTCEPSS rescore
- 2026-08-21 23:46 UTCEPSS rescore
- 2026-08-20 22:52 UTCEPSS rescore
- 2026-08-19 17:01 UTCEPSS rescore
- 2026-08-18 16:58 UTCOSV refresh
- 2026-08-18 13:45 UTCEPSS rescore
- 2026-08-17 13:44 UTCEPSS rescore
- 2026-08-16 14:53 UTCEPSS rescore
- 2026-08-16 02:11 UTCEPSS rescore
- 2026-08-15 01:27 UTCEPSS rescore
- 2026-08-13 21:57 UTCEPSS rescore
- 2026-08-12 13:48 UTCEPSS rescore
- 2026-08-11 13:38 UTCEPSS rescore
- 2026-08-09 13:44 UTCEPSS rescore
- 2026-08-08 16:34 UTCEPSS rescore
- 2026-08-07 16:24 UTCEPSS rescore
- 2026-08-06 13:44 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-04 15:07 UTCEPSS rescore
- 2026-08-04 10:35 UTCEPSS rescore
- 2026-08-03 12:27 UTCOSV refresh
- 2026-08-03 10:33 UTCEPSS rescore
- 2026-08-02 02:24 UTCEPSS rescore
- 2026-08-01 04:13 UTCEPSS rescore
- 2026-07-30 16:25 UTCEPSS rescore
- 2026-07-30 01:28 UTCEPSS rescore
- 2026-07-28 15:33 UTCEPSS rescore
- 2026-07-26 14:52 UTCEPSS rescore
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 02:09 UTCEG score recompute
- 2026-07-22 22:56 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-20 17:05 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 10:02 UTCEPSS rescore
- 2026-07-16 22:04 UTCOSV refresh
- 2026-07-16 17:00 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-13 22:27 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-12 05:44 UTCEPSS rescore
- 2026-07-12 05:44 UTCEPSS rescore
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.15:postgresql13
Same vendor
7 shownredhat:RHSA-2023:1576 · redhat:RHSA-2023:7545
Same CWE
10 shownCWE-1321 · CWE-913
Frequently asked(5)
What is CVE-2022-2625?
When was CVE-2022-2625 disclosed?
Is CVE-2022-2625 actively exploited?
What is the CVSS score of CVE-2022-2625?
How do I remediate CVE-2022-2625?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-2625
Is Your Infrastructure Affected by CVE-2022-2625?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.