CVE-2026-14662
Received Received - Intake

Integer Wraparound in PostgreSQL tsvector and tsquery Functions

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: PostgreSQL

Description
Integer wraparound in PostgreSQL tsvector and tsquery data type functions allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds, via crafted large inputs. This may execute arbitrary code as the operating system user running the database. These types are typically sourced from application logic, not taken from the application's user. Hence, application users attacking the database, through the application as a conduit, are unlikely. CVE-2026-6473 had fixed similar problems. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-13
Last Modified
2026-08-13
Generated
2026-08-13
AI Q&A
2026-08-13
EPSS Evaluated
N/A
NVD
CVE-2026-14662
EUVD
EUVD-2026-57831

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
postgresql postgresql to 18.5 (exc)
postgresql postgresql to 17.11 (exc)
postgresql postgresql to 16.15 (exc)
postgresql postgresql to 15.19 (exc)
postgresql postgresql to 14.24 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-190 The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves an integer wraparound in PostgreSQL's tsvector and tsquery data type functions. It allows an unprivileged database user to cause the server to allocate insufficient memory for large inputs, leading to out-of-bounds writes. This could potentially execute arbitrary code with the privileges of the database's operating system user.

Detection Guidance

Detecting this vulnerability requires checking the PostgreSQL version. Run 'psql --version' or 'SELECT version();' in PostgreSQL to compare against affected versions (before 18.5, 17.11, 16.15, 15.19, 14.24).

Monitor for unusual memory usage or crashes in PostgreSQL processes, as out-of-bounds writes may cause instability.

Impact Analysis

The impact includes potential arbitrary code execution on the database server, which could compromise confidentiality, integrity, and availability of data. Since the flaw stems from application logic rather than direct user input, attacks through the application are unlikely.

Compliance Impact

This vulnerability could lead to unauthorized access or data breaches, violating compliance requirements under GDPR, HIPAA, and other regulations. It may result in data exposure, integrity loss, or service disruption, requiring prompt patching to maintain compliance.

Mitigation Strategies

Upgrade PostgreSQL to the latest patched versions (18.5, 17.11, 16.15, 15.19, or 14.24) immediately. Apply the patches from August 13, 2026.

Restrict database user privileges to minimize potential impact if exploitation occurs.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-14662. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart