External risk intelligence

Postgres Enterprise Manager SQL Injection via SECURITY DEFINER Functions

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-132660

The vulnerability exists within the Postgres Enterprise Manager (PEM) backend database. While the database may be reachable over a network, it is typically an internal component used for administrative monitoring and management, sitting behind organizational controls rather than being directly exposed as a public-facing internet service.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical security issue has been identified in Postgres Enterprise Manager (PEM), affecting the PEM backend database. This vulnerability could allow unauthorized users to execute arbitrary SQL commands with superuser privileges, potentially leading to significant data compromise or system control. The primary concern is confirming if your PEM environment is exposed and requires review.

  • SQL commands can be run with high privileges.
  • This impacts PEM backend database administrative functions.
  • Confirm relevance and exposure of your PEM environment.

Attack Path

How an attacker could exploit the issue

An attacker with access to the PEM backend database could manipulate the environment to execute arbitrary SQL commands with superuser privileges. This is achieved by exploiting specific functions that incorrectly handle search paths, allowing the attacker to substitute malicious objects for legitimate ones. The vulnerability can lead to the execution of any SQL command that the superuser can run.

  • Attacker needs database access.
  • Attacker creates malicious database objects.
  • Risk of arbitrary SQL execution.

Live Threat

Current exploitation, exposure, and threat context

In the PEM backend database, several functions could allow any user to execute arbitrary SQL with superuser privileges when a safe search_path is not set. This could affect any PEM user who can connect to the database.

  • Arbitrary SQL execution with superuser privileges.
  • Creation of malicious objects in specific schemas.
  • Unauthorized access to and modification of database data.

Operational Fix

Recommended remediation, mitigation, and detection steps

Given that this vulnerability resides within the Postgres Enterprise Manager (PEM) backend database, the platform team or database administration team responsible for PEM operations is likely accountable for addressing it. The initial practical step involves identifying all PEM instances, verifying their reachability and business criticality, locating the specific ownership of each instance, and then developing a remediation plan based on the assessed risk.

  • Platform or DBA teams own the issue.
  • Verify PEM instance reachability and criticality.
  • Plan remediation based on assessed risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Postgres Enterprise Manager (PEM)?

Postgres Enterprise Manager is a management and monitoring platform designed for PostgreSQL environments. It utilizes a backend database to store administrative data, configurations, and performance metrics, allowing database administrators to oversee multiple database clusters from a centralized interface.

What is the vulnerability in CVE-2026-132660?

This issue is an Untrusted Search Path vulnerability, classified as CWE-426. It occurs because certain PEM functions run with superuser privileges but do not enforce a safe search_path. This allows an authenticated database user to trick these functions into executing malicious code instead of the intended system commands.

How does an attacker trigger this vulnerability?

An attacker needs legitimate access to connect to the PEM backend database. By creating specially crafted objects—such as temporary objects or, in certain PostgreSQL versions, objects within the public schema—the attacker can intercept the insecure search path and force the high-privilege functions to run arbitrary SQL commands.

Is my PEM instance at risk?

Halo Surface Signal indicates that while the PEM backend database might be reachable over a network, it is typically an internal component protected by organizational controls. Because it is rarely exposed as a public-facing internet service, the likelihood of external exploitation is considered low.

What should I do to address this issue?

The platform or database administration team should first identify all PEM instances and assess their reachability. If your deployment uses PEM version 10.6.1 or later, ensure you are utilizing the updated functions that enforce a fixed search_path to eliminate the risk.

References