This page was not yet optimized for use on mobile devices.
CVE-2026-50737
Data
| Vulnerability ID | CVE-2026-50737 |
|---|---|
| Published on | 28.07.2026 19:17 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:enterprisedb:pglogical:2.0.0:*:*:*:*:postgresql:*:*,
cpe:2.3:a:enterprisedb:pglogical:2.0.1:*:*:*:*:postgresql:*:*,
cpe:2.3:a:enterprisedb:pglogical:2.1.0:*:*:*:*:postgresql:*:*,
cpe:2.3:a:enterprisedb:pglogical:2.1.1:*:*:*:*:postgresql:*:*,
cpe:2.3:a:enterprisedb:pglogical:2.2.0:*:*:*:*:postgresql:*:*,
cpe:2.3:a:enterprisedb:pglogical:2.2.1:*:*:*:*:postgresql:*:*,
cpe:2.3:a:enterprisedb:pglogical:2.2.2:*:*:*:*:postgresql:*:*,
cpe:2.3:a:enterprisedb:pglogical:2.3.0:*:*:*:*:postgresql:*:*,
cpe:2.3:a:enterprisedb:pglogical:2.3.1:*:*:*:*:postgresql:*:*,
cpe:2.3:a:enterprisedb:pglogical:2.3.2:*:*:*:*:postgresql:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.