Integer wraparound in multiple PostgreSQL libpq client library functions allows an application input provider or network peer to cause libpq to undersize an allocation and write ou

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

• vendor n/a PostgreSQL 17 <17.717 <17.7

How to fix CVE-2025-12818

• Upgrade

  CVE-2025-12818 lists a fix boundary at 17.7. Compare the installed build with that boundary before you change production.

• Version check

  Seen in 17 <17.7

• Advisory

  Open the cve_org record and follow its fix.

• Official advisories

  • CVE.org · cve.org
  • EUVD · euvd.enisa.europa.eu

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Related Odoo Git fixes

Quoted Community commit messages that cite this CVE. Presence of a commit is not proof that every edition or backport includes the fix. Enterprise proprietary diffs are never shown here. Timeline

• Nov 10, 2025 · referenced

  libpq: Prevent some overflows of int/size_t

  libpq: Prevent some overflows of int/size_t Several functions could overflow their size calculations, when presented with very large inputs from remote and/or untrusted locations, and then allocate buffers that were too small to hold the intended contents. Switch from int to size_t where appropriate, and check for overflow conditions when the inputs could have plausibly originated outside of the libpq trust boundary. (Overflows from within the trust boundary are still possible, but these will be fixed separately.) A version of add_size() is ported from the backend to assist with code that performs more complicated concatenation. Reported-by: Aleksey Solovev (Positive Technologies) Reviewed-by: Noah Misch Reviewed-by: Álvaro Herrera Security: CVE-2025-12818 Backpatch-through: 13

  https://github.com/postgres/postgres/commit/600086f471a3bb57ff4953accf1d3f8d2efe0201

Timeline

Detection, updates, and resolution for this record.

1. Nov 13, 2025 · EUVD

   Detected

   Integer wraparound in multiple PostgreSQL libpq client library functions allows an application input provider or network peer to cause libpq to undersize an allocation and write out-of-bounds by hundreds of megabytes. This results in a segmentation fault for the application using libpq. Versions before PostgreSQL 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23 are affected.

2. Nov 13, 2025 · EUVD

   Updated

   Integer wraparound in multiple PostgreSQL libpq client library functions allows an application input provider or network peer to cause libpq to undersize an allocation and write out-of-bounds by hundreds of megabytes. This results in a segmentation fault for the application using libpq. Versions before PostgreSQL 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23 are affected.

Sources

• CVE.orgVulnerability recordCVE-2025-12818

  Official CVE identifier

  cve.org
• EUVDVulnerability recordEUVD-2025-169291

  Integer wraparound in multiple PostgreSQL libpq client library functions allows an application input provider or network peer to cause libpq to undersize an allocation and write out-of-bounds by hundreds of megabytes. This results in a segmentation fault for the application using

  euvd.enisa.europa.eu

References

• EUVD record · euvd.enisa.europa.eu
• EUVD reference · postgresql.org

Freshness

Last verified in this catalog Nov 3, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

• CVE.orgOct 25, 2026
• EUVDOct 25, 2026