CVE-2026-14670
Received Received - Intake

Heap Buffer Overflow in PostgreSQL plperl

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: PostgreSQL

Description
Heap buffer overflow in PostgreSQL plperl return of a tied hash allows the function owner to execute arbitrary code as the operating system user running the database, via a crafted function body. 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-14670
EUVD
EUVD-2026-57837

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-122 A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a heap buffer overflow in PostgreSQL's plperl extension. It allows a function owner to execute arbitrary code as the OS user running the database by returning a tied hash from a crafted function body. Affected versions are before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24.

Detection Guidance

Detecting this vulnerability requires checking PostgreSQL versions against affected releases. Use commands like 'psql --version' or 'postgres --version' to verify installed versions. Compare against 18.5, 17.11, 16.15, 15.19, and 14.24. If your version is older, the system is vulnerable.

Impact Analysis

An attacker with function ownership could execute arbitrary code, potentially gaining full control over the database server. This could lead to data theft, manipulation, or system compromise. The high CVSS score (8.8) reflects the significant risk.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's integrity and confidentiality requirements or HIPAA's security rules. Non-compliance risks include fines and legal penalties.

Mitigation Strategies

Immediately update PostgreSQL to versions 18.5, 17.11, 16.15, 15.19, or 14.24 or later. Remove or restrict access to plperl functions owned by untrusted users until patched. Monitor database logs for suspicious activity related to plperl function execution.

Chat Assistant

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

EPSS Chart