Skip to content
VulniPulse
Advisory severityHigh8.8Red Hat Linux

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.0 Extended Update Support, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-14670 Source published Source updated

VulniPulse record published Record updated

CVE-2026-14670
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

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 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

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 products named by the advisory: Red Hat Enterprise Linux 10.0 Extended Update Support; Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support; Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On; Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support; and 11 more.

Affected versions
  • < 18.5
  • < 17.11
  • < 16.15
  • < 15.19
  • < 14.24

Official advisory · high-confidence parse· fetched 15 days ago·verify at source

Fixed versions
  • postgresql18-0:18.6-1.el10_2
  • postgresql16-0:16.15-1.el10_2
  • postgresql16-0:16.15-1.el10_0
  • postgresql:16-8100020260910192321.489197e6
  • postgresql:15-8100020260906175012.489197e6
  • postgresql:12-8100020260917081510.489197e6
  • postgresql:12-8040020260924163759.522a0ee4
  • postgresql:12-8060020260923144955.ad008a3a
  • postgresql:15-8080020260921162003.63b34585
  • postgresql:12-8080020260923144922.63b34585
  • postgresql:16-9080020260907191505.rhel9
  • postgresql:18-9080020260914093252.rhel9
  • postgresql-0:13.23-6.el9_8
  • postgresql:15-9080020260903073937.rhel9
  • postgresql-0:13.23-1.el9_2.5
  • postgresql:15-9040020260917091622.rhel9
  • postgresql:16-9040020260922062609.rhel9
  • postgresql-0:13.23-1.el9_4.4
  • postgresql:16-9060020260921091101.rhel9
  • postgresql-0:13.23-1.el9_6.5
  • ansible-automation-platform/bootc-automation-portal-rhel9:1790657374
  • rhui5/rhua-rhel9:1790242004
  • RHSA-2026:67280
  • RHSA-2026:70186
  • RHSA-2026:72282
  • RHSA-2026:69876
  • RHSA-2026:69923
  • RHSA-2026:69924
  • RHSA-2026:73912
  • RHSA-2026:72363
  • RHSA-2026:70602
  • RHSA-2026:72362
  • RHSA-2026:67491
  • RHSA-2026:67848
  • RHSA-2026:69607
  • RHSA-2026:69914
  • RHSA-2026:72361
  • RHSA-2026:70762
  • RHSA-2026:70856
  • RHSA-2026:72283
  • RHSA-2026:70559
  • RHSA-2026:72281

Official advisory · high-confidence parse· fetched 15 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • 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 15 days 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.