High [CVE-2026-14670] Arbitrary code execution via plperl tied hash heap buffer overflow
This high-severity Red Hat Linux advisory covers CVE-2026-14670 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
A flaw was found in PostgreSQL. This could lead to unauthorized access and control over the database system.
By crafting a malicious function body, an attacker with low privileges can exploit a heap buffer overflow, leading to full compromise of the database system. Red Hat severity: Important — CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
Weakness: CWE-805. Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Self-service automation portal 2.
Red Hat lists Red Hat Enterprise Linux 6; Red Hat Hardened Images as not affected. Red Hat does not currently list a fixing RHSA for this CVE.
Affected products named by the advisory: Red Hat package: postgresql16; Red Hat package: postgresql18.
- < 18.5
- < 17.11
- < 16.15
- < 15.19
- < 14.24
Official advisory · high-confidence parse· fetched 55 minutes ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 55 minutes ago·verify at source
Mitigation checklist
- Disable the plperl procedural language if it is not actively required by executing DROP LANGUAGE plperl; on affected databases. Alternatively, restrict access by revoking USAGE privileges on plperl from untrusted roles. These actions prevent the execution of crafted plperl functions, mitigating the risk(a database restart may be required to clear active sessions).
Official advisory · high-confidence parse· fetched 55 minutes ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.