Skip to main content
Menu
CVEs

EnterpriseDB Postgres Enterprise Manager remote code execution via SECURITY DEFINER search path

CVE-2026-132660Published , updated

9.4CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 10.6.1
Who is exposed
Not reported

Summary

EnterpriseDB's Postgres Enterprise Manager has several privileged database functions that don't use a safe search path, so a user who can connect to its backend database can plant objects that the functions use in their place. Over the network with only a low-privilege login and no user interaction, an attacker can use this to run arbitrary SQL with superuser privileges.

Written by a model

Original description

In Postgres Enterprise Manager (PEM), several SECURITY DEFINER functions in the pem schema of the PEM backend database are owned by a superuser but do not set a safe search_path. Any PEM user who can connect to the PEM backend database can create objects that these functions use in place of the intended ones, and so run arbitrary SQL with superuser privileges. Temporary objects can be used for this on every supported PostgreSQL version, and objects in the public schema on PostgreSQL 14 backends and backends upgraded from PostgreSQL 14. From PEM 10.6.1, these functions run with a fixed search_path.

What to do

Upgrade to a fixed version: 10.6.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-132660 (In Postgres Enterprise Manager (PEM), several SECURITY DEFINER functions in the pem schema of the PEM backend database are owned by a…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-132660 (entry last updated 2026-11-20):
Affected:
- EnterpriseDB Postgres Enterprise Manager: from 7.6.0, fixed in 10.6.1
Fixed versions: 10.6.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132660 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132660 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.enterprisedb.com/docs/security/advisories/cve2026132660/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-132660
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132660"}.

Affected versions

cve.now Index

29Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach17/20Affects PostgreSQL (a widely deployed server, runtime, framework or database)
  • Severity9.4/10CVSS 9.4
  • No patch0/5No signal

What would change the score

  • Would score about 84 if added to CISA KEV
  • Would score about 79 if CISA's SSVC rates exploitation active
  • Would score about 48 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkenterprisedb.com · docs/security/advisories/cve2026132660
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-132660
RecordNVD · CVE-2026-132660

Questions about CVE-2026-132660

Is CVE-2026-132660 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-132660?

Postgres Enterprise Manager: from 7.6.0 before 10.6.1.

Source: cve.now feed data

How do I fix CVE-2026-132660?

Upgrade to a fixed version: 10.6.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.