UBUNTU-CVE-2026-16237: Medium severity ubuntu/postgresql-9.3 vulnerability

Published Nov 13, 2026
·
Updated

Improper protection in PostgreSQL INSERT ... ON CONFLICT on auto-updatable views allows an attacker having INSERT and UPDATE privileges on the view to read and modify every row in the view's base table, via iterated INSERT ... ON CONFLICT DO UPDATE. This bypasses the view's WHERE condition, whether or not the view is a securitybarrier view. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Affected Software

8 affected components
ubuntu/postgresql-9.3*
ubuntu/postgresql-9.5*
ubuntu/postgresql-10*
ubuntu/postgresql-12*
ubuntu/postgresql-14*
ubuntu/postgresql-16*
ubuntu/postgresql-18*
ubuntu/postgresql-18*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.7
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.12
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.16
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 15.20
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 14.25

Event History

Nov 13, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments are exposed when an auto-updatable view has a WHERE condition and a user has both INSERT and UPDATE privileges on that view. The issue affects PostgreSQL versions before 18.7, 17.12, 16.16, 15.20, and 14.25.

2

What access does an attacker need?

An attacker needs INSERT and UPDATE privileges on the affected view. They can use iterated INSERT ... ON CONFLICT DO UPDATE operations to read and modify rows in the underlying base table that the view's WHERE condition should restrict.

3

Does marking the view as security_barrier prevent exploitation?

No. The described bypass applies whether or not the affected view is configured as a security_barrier view.

4

How can administrators identify potentially affected configurations?

Identify auto-updatable views with WHERE conditions, then review which roles have both INSERT and UPDATE privileges on those views. Systems running releases earlier than the listed fixed versions should be assessed for those privilege and view combinations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203