CVE EVIDENCE REVIEW
ReviewHighEvidence review

CVE-2026-14664 evidence review

PostgreSQL, postgresql

Heap buffer overflow in PostgreSQL regexp allows the query author to execute arbitrary code as the operating system user running the database, via text that would not pass encoding validation. This shares heritage with CVE-2026-2006, but this case involved unanticipated data growth when round-tripped through pg_wchar. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.

Open CVE record
Evidence review

This record remains available for product and version identification, but it is not presented as a complete remediation procedure. Confirm the affected range and the supported fix in a direct vendor advisory before changing production systems.

ProductPostgreSQL, postgresql
Affected versions>= 18 < 18.5, >= 17 < 17.11, >= 16 < 16.15, >= 15 < 15.19, >= 14.0 < 14.24, >= 15.0 < 15.19, >= 16.0 < 16.15, >= 17.0 < 17.11, >= 18.0 < 18.5
Fixed versionsVerify the fixed release separately for each affected product line
Priority basisReview · CVSS 8.8 · EPSS 0.44%
01

Identify the product and installed version

Record whether PostgreSQL, postgresql is present, where it is installed, and which interfaces are exposed.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Compare the affected range

Use the current record as an identification aid: >= 18 < 18.5, >= 17 < 17.11, >= 16 < 16.15, >= 15 < 15.19, >= 14.0 < 14.24, >= 15.0 < 15.19, >= 16.0 < 16.15, >= 17.0 < 17.11, >= 18.0 < 18.5. Resolve incomplete inventory results before deciding that an asset is unaffected.

03

Verify the authoritative remediation source

Open the linked source material and locate a direct vendor advisory for this CVE. Confirm the supported fixed release and product-specific update path before making a production change.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.