CVE-2022-1552: PostgreSQL Maintenance Operation Sandbox Bypass and Privilege Escalation
- Vendor
- Postgresql
CVE-2022-1552 is a privilege-escalation vulnerability in PostgreSQL caused by missing or delayed enforcement of the security-restricted-operation sandbox when privileged users maintain objects owned by other users. Affected operations include autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and pg_amcheck. An attacker permitted to create non-temporary objects in at least one schema can execute arbitrary SQL functions under a database superuser identity. Affected supported branches at disclosure were PostgreSQL 10 through 14, before releases 10.21, 11.16, 12.11, 13.7, and 14.3, respectively. Older unsupported versions were not generally tested.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises database confidentiality, integrity, and availability by allowing attacker-controlled SQL functions to execute with superuser privileges. Consequences include disclosure of sensitive information, unauthorized addition or modification of data, and denial of service.
Mitigation
If you can’t patch tonight, do this now.
If patching is temporarily impossible, disable autovacuum, avoid manually executing REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and pg_amcheck against untrusted users' objects, and do not restore pg_dump output. VACUUM is safe, and the affected commands are safe when a trusted user owns the target object. This workaround can cause database performance to degrade quickly and is not a substitute for updating.
Remediation
Patch, then assume compromise.
Upgrade PostgreSQL to version 14.3, 13.7, 12.11, 11.16, or 10.21 or a later fixed release in the corresponding branch. For vendor-packaged or embedded deployments, apply the applicable vendor security update. PostgreSQL minor-version updates do not require a database dump and reload or pg_upgrade; stop the server, update the binaries, and restart it.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2022-1552 exploited in the wild?
- As of Nov 11, 2026, Mallory has no reports of CVE-2022-1552 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2022-1552?
- As of Nov 11, 2026, Mallory has found no public exploit for CVE-2022-1552.
- Is there a patch for CVE-2022-1552?
- Upgrade PostgreSQL to version 14.3, 13.7, 12.11, 11.16, or 10.21 or a later fixed release in the corresponding branch. For vendor-packaged or embedded deployments, apply the applicable vendor security update.
- What products are affected by CVE-2022-1552?
- Postgresql.
- How severe is CVE-2022-1552?
- CVE-2022-1552 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 16.3% (97th percentile) as of Nov 11, 2026.
Recent activity
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.