CVE-2026-116326
Received Received - Intake

Uncaught Exception Handling Flaw in PostgreSQL plperl

Vulnerability report for CVE-2026-116326, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-12

Last updated on: 2026-11-12

Assigner: PostgreSQL

Description

Uncaught exceptions in PostgreSQL plperl allow an object creator to cause use of a stale sigjmp_buf, via a tied Perl object, or a Perl object whose overloaded conversion throws while plperl is handling another error. We have not ruled out arbitrary code execution on some platform. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-12
Last Modified
2026-11-12
Generated
2026-11-12
AI Q&A
2026-11-12
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
postgresql postgresql to 18.7 (exc)
postgresql postgresql to 17.12 (exc)
postgresql postgresql to 16.16 (exc)
postgresql postgresql to 15.20 (exc)
postgresql postgresql to 14.25 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-672 The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves uncaught exceptions in PostgreSQL's plperl extension. An object creator can exploit tied Perl objects or overloaded conversions to throw exceptions while PostgreSQL handles another error. This may lead to the use of a stale sigjmp_buf, potentially enabling arbitrary code execution on some platforms.

Detection Guidance

Detecting this vulnerability requires checking the PostgreSQL version installed on your system. Use the command 'psql --version' to verify if your version is below 18.7, 17.12, 16.16, 15.20, or 14.25. If so, the system is vulnerable.

Impact Analysis

An attacker with the ability to create Perl objects could exploit this to execute arbitrary code, potentially gaining control over the database server. This could lead to data breaches, unauthorized access, or system compromise.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating confidentiality and integrity requirements in GDPR and HIPAA. Non-compliance may result in legal penalties, fines, or reputational damage.

Mitigation Strategies

Immediately update PostgreSQL to a patched version (18.7 or later, 17.12 or later, 16.16 or later, 15.20 or later, or 14.25 or later). Disable the plperl extension if not required. Monitor PostgreSQL logs for unusual activity.

Chat Assistant

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

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...