CVE-2026-120153: PostgreSQL extension-script substitutions allow SQL injection through object names

Published Nov 12, 2026
·
Updated

SQL injection in PostgreSQL extension-script substitutions allows an attacker with database-level CREATE privilege to execute arbitrary code as the bootstrap superuser, via a schema or owner name containing newlines or other special substrings. This is similar to CVE-2023-39417, but it requires a non-bundled extension with a vulnerable script pattern. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 18.7
  2. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 17.12
  3. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 16.16
  4. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 15.20
  5. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 14.25

Event History

Nov 12, 2026
CVE Published
via MITRE·02:15 PM
Data Sourced
via MITRE·02:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are actually affected?

Affected deployments use PostgreSQL versions before 18.7, 17.12, 16.16, 15.20, or 14.25 and have a non-bundled extension whose script uses the vulnerable substitution pattern. The issue does not apply solely because PostgreSQL is installed; the vulnerable extension-script pattern must be present.

2

What access does an attacker need?

An attacker needs database-level CREATE privilege. They can use a schema or owner name containing newlines or other special substrings to exploit vulnerable extension-script substitutions.

3

What is the impact of successful exploitation?

Successful exploitation can allow arbitrary code execution as the bootstrap superuser. This can affect confidentiality, integrity, and availability.

4

What should be prioritized for remediation?

Upgrade PostgreSQL to 18.7, 17.12, 16.16, 15.20, or 14.25, as applicable. Also identify non-bundled extensions and review their scripts for vulnerable substitution patterns involving schema or owner names.

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