PostgreSQL
PostgreSQL tsvector and tsquery undersize allocations, via integer wraparound
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.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 18, < 18.6
- >= 17, < 17.11
- >= 16, < 16.15
- >= 15, < 15.19
- < 14.24
Fixed in 18.6, 17.11, 16.15, 15.19, 14.24
Mitigation
Upgrade PostgreSQL to 18.6 or 17.11 or 16.15 or 15.19 or 14.24 or later.
Timeline
Days relative to CVE publicationFirst public PoC 19 days after publication; not in CISA KEV. First PoC: Kihara-1/postgresql-cve-2026-14662 (created 1 Sep 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Kihara-1/postgresql-cve-2026-14662 | 1 Sep 2026 +19 d | 0 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.