CVE-2026-16241: PostgreSQL ECPG integer underflow can crash the client

Published Aug 13, 2026
·
Updated

Integer underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of service against the ECPG client via sending a bytea value lacking the mandatory prefix. The client overwrites a huge memory region with bytes outside attacker knowledge or control. This typically yields a simple SIGSEGV, but rare cases might achieve client-specific integrity impact via the write. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.

Affected Software

1 affected component
PostgreSQL PostgreSQL ECPG<18.5, <17.11, <16.15, <15.19, <14.24

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PostgreSQL ECPG to a version that resolves this vulnerability.

    Fixed in 18.5
  2. Upgrade

    Upgrade PostgreSQL ECPG to a version that resolves this vulnerability.

    Fixed in 17.11
  3. Upgrade

    Upgrade PostgreSQL ECPG to a version that resolves this vulnerability.

    Fixed in 16.15
  4. Upgrade

    Upgrade PostgreSQL ECPG to a version that resolves this vulnerability.

    Fixed in 15.19
  5. Upgrade

    Upgrade PostgreSQL ECPG to a version that resolves this vulnerability.

    Fixed in 14.24

Event History

Aug 13, 2026
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-16241?

The severity of CVE-2026-16241 is classified as low with a score of 3.8.

2

How does CVE-2026-16241 affect PostgreSQL users?

CVE-2026-16241 can crash the ECPG client, causing a temporary denial of service for users.

3

What is the risk associated with CVE-2026-16241?

CVE-2026-16241 poses a risk level of 26, indicating a low impact vulnerability.

4

What is the main cause of CVE-2026-16241?

The main cause of CVE-2026-16241 is an integer underflow in the PostgreSQL ECPG module.

5

How can I mitigate the risks of CVE-2026-16241?

To mitigate the risks of CVE-2026-16241, ensure to use a patched version of PostgreSQL that addresses this vulnerability.

Company

Resources

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
CVE-2026-16241 - PostgreSQL ECPG integer underflow can crash the client - SecAlerts