dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2026-14662

HIGH · 8.8 CVSS v3.1 Developing Published 2026-08-13
No fix yet
No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 6 days old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-27.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Recommended fix High confidence

PostgreSQL 18.5 (or the latest stable release in your current major version branch)

  1. Identify the current PostgreSQL major version by running: psql -c 'SELECT version();'
  2. For PostgreSQL 14.x: Upgrade to version 14.24 or later
  3. For PostgreSQL 15.x: Upgrade to version 15.19 or later
  4. For PostgreSQL 16.x: Upgrade to version 16.15 or later
  5. For PostgreSQL 17.x: Upgrade to version 17.11 or later
  6. For PostgreSQL 18.x: Upgrade to version 18.5 or later
  7. Use pg_upgrade or pg_dump/pg_restore to apply the upgrade, following PostgreSQL upgrade procedures
  8. After upgrade, verify the new version: psql -c 'SELECT version();'
Caveat Minor version upgrades (e.g., 17.x to 17.11) are generally safe with in-place upgrades; major version upgrades (e.g., 17.x to 18.x) require pg_dump/pg_restore or pg_upgrade and may have compatibility changes

Generated from the published advisory — verify against the referenced sources before acting.

No vendor fix exists The vendor has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $8,000. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14662 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data