CVE-2022-1552 [High] | Security Vulnerability in Postgresql

A flaw was found in PostgreSQL. There is an issue with incomplete efforts to operate safely when a privileged user is maintaining another user's objects. The Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and pg_amcheck commands activated relevant protections too late or not at all during the process. This flaw allows an attacker with permission to create non-temporary objects in at least one schema to execute arbitrary SQL functions under a superuser identity.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	2.26%	11.73%	+9.46%
2	2026-03-17	3.04%	2.26%	-0.78%
3	2026-03-04	—	3.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

2.26%

11.73%

+9.46%

2026-03-17

3.04%

2.26%

-0.78%

2026-03-04

—

3.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

OS Trackers for CVE-2022-1552

vendor	priority	summary	link
`alpine`	high	CVE-2022-1552: 5 source package rows (postgresql, postgresql12, postgresql13, postgresql14, postgresql15); 36 state rows across 10 repos (3.17-community, 3.17-main, 3.18-community, 3.18-main, 3.19-community, 3.19-main, 3.20-community, 3.20-main, edge-community, edge-main); fixed 21, open 15.	https://security.alpinelinux.org/vuln/CVE-2022-1552
`debian`	not yet assigned	CVE-2022-1552 not yet assigned priority: Debian including 1 source packages (postgresql-13), 1 status rows across 1 suites (bullseye): resolved 1.	https://security-tracker.debian.org/tracker/CVE-2022-1552
`gentoo`	high	CVE-2022-1552: 1 GLSA(s) (202211-04), 1 atom(s) (dev-db/postgresql); latest impact high.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-1552
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2022-1552
`suse`	high	CVE-2022-1552 severity important: SUSE including 608 source package names (12.14-21.1:libpq5-14.3-150200.5.12.2, 12.14-21.1:postgresql12-12.11-150200.8.32.1, …), 1770 product×package rows across 85 product lines (Container suse/postgres, Container trento/trento-db, … (85 product lines)): Fixed 1474, Known Affected 231, Known Not Affected 65.	https://www.suse.com/security/cve/CVE-2022-1552/
`ubuntu`	medium	CVE-2022-1552 medium priority: Ubuntu including 7 source packages (postgresql-10, postgresql-12, …), 98 status rows across 14 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 84, released 7, ignored 4, deferred 1, needs-triage 1, not-affected 1.	https://ubuntu.com/security/CVE-2022-1552

Affected software / configurations for CVE-2022-1552

Vendor	Product	Version	Raw CPE
postgresql	postgresql	>= 10.0, < 10.21	cpe:2.3:a:postgresql:postgresql::::::::
postgresql	postgresql	>= 11.0, < 11.16	cpe:2.3:a:postgresql:postgresql::::::::
postgresql	postgresql	>= 12.0, < 12.11	cpe:2.3:a:postgresql:postgresql::::::::
postgresql	postgresql	>= 13.0, < 13.7	cpe:2.3:a:postgresql:postgresql::::::::
postgresql	postgresql	>= 14.0, < 14.3	cpe:2.3:a:postgresql:postgresql::::::::

References for CVE-2022-1552

URL	Tags
https://access.redhat.com/security/cve/CVE-2022-1552	Third Party Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=2081126	Issue Tracking Patch Third Party Advisory
https://security.gentoo.org/glsa/202211-04	Third Party Advisory
https://security.netapp.com/advisory/ntap-20221104-0005/	Third Party Advisory
https://www.postgresql.org/about/news/postgresql-143-137-1211-1116-and-1021-released-2449/	Vendor Advisory
https://www.postgresql.org/support/security/CVE-2022-1552/	Vendor Advisory

URL

CVE-2022-1552

Exploit prediction scoring system (EPSS) score for CVE-2022-1552

Common vulnerability scoring system (CVSS) metrics for CVE-2022-1552

Weakness enumeration for CVE-2022-1552

OS Trackers for CVE-2022-1552

Affected software / configurations for CVE-2022-1552

References for CVE-2022-1552