EnterpriseDB Postgres Enterprise Manager authorization bypass in webhook function
- Exploited
- No known exploitation
- Fix
- Fixed in 10.6.1
- Who is exposed
- Not reported
Summary
Any authenticated Postgres Enterprise Manager user can reach this flaw over the network by running a function that sends queued payloads to configured webhooks. Doing so lets them send forged notifications, using the stored headers, OAuth token, or client certificate, to endpoints they could not otherwise authenticate to.
Written by a model
Original 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.
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-132668 (In Postgres Enterprise Manager (PEM), any PEM user can run the pem.send_webhook() function, which runs with elevated privileges and queues…), 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-132668 (entry last updated 2026-11-20):
Affected:
- EnterpriseDB Postgres Enterprise Manager: from 8.0.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-132668 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132668 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/cve2026132668/
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-132668
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-132668"}.Affected versions
- EnterpriseDB Postgres Enterprise ManagerFrom 8.0.0 · fixed in 10.6.1
cve.now Index
- 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)
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | enterprisedb.com · docs/security/advisories/cve2026132668 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132668 |
| Record | NVD · CVE-2026-132668 |
Questions about CVE-2026-132668
Is CVE-2026-132668 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-132668?
Postgres Enterprise Manager: from 8.0.0 before 10.6.1.
Source: cve.now feed data
How do I fix CVE-2026-132668?
Upgrade to a fixed version: 10.6.1.
Source: cve.now feed data
Related
- CVE-2026-132660In Postgres Enterprise Manager (PEM), several SECURITY DEFINER functions in the pem schema of the PEM backend database are owned by a…
- CVE-2026-132659In Postgres Enterprise Manager (PEM), the row-level security policies on pem.job and pem.jobstep that apply to PEM agents do not limit an…
- CVE-2026-132658In Postgres Enterprise Manager (PEM), the pem_agent role, which every PEM agent login inherits, is a member of the PostgreSQL…
- CVE-2026-132661In Postgres Enterprise Manager (PEM), multi-factor authentication (MFA) is not enforced on the PEM web application's own routes.
- CVE-2026-132662In Postgres Enterprise Manager (PEM), the SQL Profiler save and load functions in the PEM web application do not keep the client-supplied…
- CVE-2026-132663In Postgres Enterprise Manager (PEM), webhook URLs are not validated, and the PEM agent does not restrict the URL schemes it uses to…
No corrections so far. Something wrong on this page? Report an error.