CVE-2025-4207: PostgreSQL GB18030 encoding validation can read one byte past end of allocation for text that fails validation

Published May 8, 2025
·
Updated

Buffer over-read in PostgreSQL GB18030 encoding validation allows a database input provider to achieve temporary denial of service on platforms where a 1-byte over-read can elicit process termination. This affects the database server and also libpq. Versions before PostgreSQL 17.5, 16.9, 15.13, 14.18, and 13.21 are affected.

Other sources

PostgreSQL GB18030 encoding validation can read one byte past end of allocation for text that fails validation

— Microsoft

Affected Software

8 affected componentsFixes available
PostgreSQL postgresql<17.5, <16.9, <15.13, <14.18, <13.21
PostgreSQL libpq<17.5, <16.9, <15.13, <14.18, <13.21
Microsoft cbl2 postgresql 14.16-1<14.18-1
14.18-1
Microsoft azl3 rust 1.90.0-4<1.90.0-4
1.90.0-4
Microsoft azl3 postgresql 16.7-1<16.9-1
16.9-1
Microsoft cm2 postgresql 14.18-1<14.18-1
14.18-1
Microsoft azl3 rust 1.90.0-3<1.90.0-4
1.90.0-4
Microsoft azl3 postgresql 16.9-1<16.9-1
16.9-1

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 1.90.0-4
  2. Upgrade

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

    Fixed in 14.18-1
  3. Upgrade

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

    Fixed in 16.9-1
  4. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 17.5
  5. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 16.9
  6. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 15.13
  7. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 14.18
  8. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 13.21

Event History

May 8, 2025
CVE Published
via MITRE·02:22 PM
Data Sourced
via MITRE·02:22 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeakness
Jul 11, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2025-4207?

CVE-2025-4207 has a high severity due to its potential to cause a temporary denial of service.

2

What is affected by CVE-2025-4207?

CVE-2025-4207 affects PostgreSQL versions before 17.5 and libpq versions before 17.5.

3

How do I fix CVE-2025-4207?

To fix CVE-2025-4207, upgrade PostgreSQL and libpq to version 17.5 or later.

4

What type of vulnerability is CVE-2025-4207?

CVE-2025-4207 is a buffer over-read vulnerability.

5

How can CVE-2025-4207 impact my PostgreSQL database?

CVE-2025-4207 can lead to process termination resulting in temporary denial of service for your PostgreSQL database.

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