37 matches found
EUVD-2026-131605
In Postgres Enterprise Manager PEM, any PEM user can read the encrypted passwords that PEM agents use to connect to monitored servers, including the PEM backend superuser password stored when the PEM server is configured. Unless a custom encryption key is configured, these passwords are encrypted...
EUVD-2026-131607
In Postgres Enterprise Manager PEM, any PEM user can run the pem.sendwebhook 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 forg...
EUVD-2026-131604
In Postgres Enterprise Manager PEM, webhook URLs are not validated, and the PEM agent does not restrict the URL schemes it uses to deliver webhooks. A user with the alert configuration role pemconfigalert can set up a webhook with a file:// URL. When the webhook is sent, the agent on the PEM...
EUVD-2026-131603
In Postgres Enterprise Manager PEM, the SQL Profiler save and load functions in the PEM web application do not keep the client-supplied file name inside the user's storage directory. A user with the SQL Profiler role pemcompsqlprofiler can read JSON files, and overwrite files that the PEM web...
EUVD-2026-131606
In Postgres Enterprise Manager PEM, the pem.deployjobtemplate function does not check that the caller can access the servers, groups and agents it deploys a job template to. When PEM teams are used to separate access, a user with the scheduled tasks role pemmanagescheduletask can deploy and...
EUVD-2026-131600
In Postgres Enterprise Manager PEM, the row-level security policies on pem.job and pem.jobstep that apply to PEM agents do not limit an agent to its own jobs. An attacker who controls one monitored host, and so its PEM agent certificate, can create, change or delete jobs for every other agent,...
EUVD-2026-131599
In Postgres Enterprise Manager PEM, the pemagent role, which every PEM agent login inherits, is a member of the PostgreSQL pgreadserverfiles and pgwriteserverfiles roles on the PEM backend database. An attacker who controls any monitored host, and so its PEM agent certificate, can read and write...
EUVD-2026-131602
In Postgres Enterprise Manager PEM, multi-factor authentication MFA is not enforced on the PEM web application's own routes. An attacker who knows the password of a user who has enrolled a second factor can skip the second factor and call PEM's pages and APIs directly, with that user's permission...
EUVD-2026-131601
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 searchpath. Any PEM user who can connect to the PEM backend database can create objects that these functions use in place of the...
CVE-2026-132662
In Postgres Enterprise Manager PEM, the SQL Profiler save and load functions in the PEM web application do not keep the client-supplied file name inside the user's storage directory. A user with the SQL Profiler role pemcompsqlprofiler can read JSON files, and overwrite files that the PEM web...
CVE-2026-132668
In Postgres Enterprise Manager PEM, any PEM user can run the pem.sendwebhook 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 forg...
CVE-2026-132664
In Postgres Enterprise Manager PEM, any PEM user can read the encrypted passwords that PEM agents use to connect to monitored servers, including the PEM backend superuser password stored when the PEM server is configured. Unless a custom encryption key is configured, these passwords are encrypted...
CVE-2026-132665
In Postgres Enterprise Manager PEM, the pem.deployjobtemplate function does not check that the caller can access the servers, groups and agents it deploys a job template to. When PEM teams are used to separate access, a user with the scheduled tasks role pemmanagescheduletask can deploy and...
CVE-2026-132663
In Postgres Enterprise Manager PEM, webhook URLs are not validated, and the PEM agent does not restrict the URL schemes it uses to deliver webhooks. A user with the alert configuration role pemconfigalert can set up a webhook with a file:// URL. When the webhook is sent, the agent on the PEM...
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 superuser but do not set a safe searchpath. Any PEM user who can connect to the PEM backend database can create objects that these functions use in place of the...
CVE-2026-132661
In Postgres Enterprise Manager PEM, multi-factor authentication MFA is not enforced on the PEM web application's own routes. An attacker who knows the password of a user who has enrolled a second factor can skip the second factor and call PEM's pages and APIs directly, with that user's permission...
CVE-2026-132659
In Postgres Enterprise Manager PEM, the row-level security policies on pem.job and pem.jobstep that apply to PEM agents do not limit an agent to its own jobs. An attacker who controls one monitored host, and so its PEM agent certificate, can create, change or delete jobs for every other agent,...
CVE-2026-132658
In Postgres Enterprise Manager PEM, the pemagent role, which every PEM agent login inherits, is a member of the PostgreSQL pgreadserverfiles and pgwriteserverfiles roles on the PEM backend database. An attacker who controls any monitored host, and so its PEM agent certificate, can read and write...
CVE-2026-132665
In Postgres Enterprise Manager PEM, the pem.deployjobtemplate function does not check that the caller can access the servers, groups and agents it deploys a job template to. When PEM teams are used to separate access, a user with the scheduled tasks role pemmanagescheduletask can deploy and...
CVE-2026-132668
In Postgres Enterprise Manager (PEM) , any user can execute the pem.send_webhook() function. This function operates with elevated privileges to queue payloads for configured webhooks. The PEM agent delivers these payloads using the webhook's stored headers, OAuth tokens, or client certificates , ...