dbcve.org
PostgreSQLDatabase / datastore

CVE-2026-14680

HIGH · 8.8 CVSS v3.1 Published 2026-08-13
Fix available
A fix is available. Upgrade to 14.24 / 15.19 or later.
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
Type confusion with PostgreSQL "internal" data type arguments allows any user to execute arbitrary code as the operating system user running the database, via calls to functions with that argument type. Type "internal" represents a class of mutually-incompatible data structures not intended for access from SQL. The system intended to prevent such function calls, but this prevention had gaps. 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
How this class of weakness works · CWE-843

A resource is accessed as one type when it was actually allocated as another, so the code misreads memory layout — in interpreters and language runtimes this is frequently a direct path to code execution. It often arises from unchecked casts on attacker-influenced objects. The fix is strict type checks before casts and memory-safe access patterns.

General guidance for the type confusion class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PostgreSQLDatabase / datastore
Affected:>= 14.0, < 14.24>= 15.0, < 15.19>= 16.0, < 16.15>= 17.0, < 17.11>= 18.0, < 18.5

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
Upgrade available Upgrade to 14.24 / 15.19 / 16.15 or later
Fixed in 14.2415.1916.15
Recommended fix High confidence

PostgreSQL 14.24, 15.19, 16.15, 17.11, or 18.5 (depending on your current major version line)

  1. 1. Identify the current PostgreSQL version by running: psql --version or SELECT version();
  2. 2. Determine which major version line you are on (14, 15, 16, 17, or 18)
  3. 3. Plan upgrade to the corresponding fixed release: if on 14.x upgrade to 14.24, on 15.x to 15.19, on 16.x to 16.15, on 17.x to 17.11, or on 18.x to 18.5
  4. 4. Perform a full backup of all databases before upgrading: pg_dumpall -f backup.sql or use pg_basebackup for point-in-time recovery
  5. 5. Stop the PostgreSQL service: sudo systemctl stop postgresql (or equivalent for your system)
  6. 6. Upgrade PostgreSQL packages using your system's package manager (apt, yum, dnf, or compile from source)
  7. 7. Start the PostgreSQL service: sudo systemctl start postgresql
  8. 8. Run pg_upgrade if upgrading between major versions, or simply start the service if upgrading within the same major version
Caveat Upgrading PostgreSQL may require changes to configuration files, potential application compatibility testing, and review of deprecated features - major version upgrades in particular require pg_upgrade and thorough testing

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $4,900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14680 — 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-14680 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