From PEM 10.6.1, no PEM login role can call this function directly. PEM still sends webhook notifications through its own internal paths.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 20 Nov 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Enterprisedb
Enterprisedb postgres Enterprise Manager |
|
| Vendors & Products |
Enterprisedb
Enterprisedb postgres Enterprise Manager |
Fri, 20 Nov 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Postgres Enterprise Manager (PEM), any PEM user can run the pem.send_webhook() function, which runs with elevated privileges and queues a payload for any configured webhook. The PEM agent then delivers it with that webhook's stored headers, OAuth token or client certificate, so a user can send forged notifications to endpoints they could not otherwise authenticate to. From PEM 10.6.1, no PEM login role can call this function directly. PEM still sends webhook notifications through its own internal paths. | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: EDB
Published:
Updated: 2026-11-20T16:30:29.223Z
Reserved: 2026-11-18T22:28:03.913Z
Link: CVE-2026-132668
No data.
Status : Received
Published: 2026-11-20T15:17:48.607
Modified: 2026-11-20T17:18:14.350
Link: CVE-2026-132668
No data.
OpenCVE Enrichment
Updated: 2026-11-20T18:30:21Z