CVE-2026-132661: In Postgres Enterprise Manager (PEM), multi-factor authentication (MFA) is not enforced on the PEM
Source GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.6 High : upgrade to 10.6.1 soon.
Data as of 20 Nov 2026, 16:19 UTC
Thin evidence
One scorer or none| CNA (EDB) | CVSS 4.0 | 7.6 |
|---|
- Patch
- Available – fixed in 10.6.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Postgres Enterprise Manager to 10.6.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EnterpriseDBPostgres Enterprise Manager | Affected
| Fixed in
|
AI-suggested
Upgrade to Postgres Enterprise Manager version 10.6.1 or later, where MFA enforcement is applied to all authenticated routes. This official fix ensures that the second factor is required for all PEM web application access, preventing bypass of MFA.
Description
Postgres Enterprise Manager (PEM) versions prior to 10.6.1 do not enforce multi-factor authentication (MFA) on the PEM web application's own routes. This allows an attacker who knows a user's password, even if that user has enrolled a second factor, to bypass the second factor and access PEM pages and APIs with that user's permissions. Starting from PEM 10.6.1, MFA enforcement is applied to all authenticated PEM routes.