This page was not yet optimized for use on mobile devices.
CVE-2026-17349
Data
| Vulnerability ID | CVE-2026-17349 |
|---|---|
| Published on | 31.07.2026 16:16 |
| Severity | CRITICAL |
Vulnerable configurations
-
cpe:2.3:a:pgadmin:pgadmin_4:9.0:*:*:*:*:postgresql:*:*,
cpe:2.3:a:pgadmin:pgadmin_4:9.1:*:*:*:*:postgresql:*:*,
cpe:2.3:a:pgadmin:pgadmin_4:9.2:*:*:*:*:postgresql:*:*,
cpe:2.3:a:pgadmin:pgadmin_4:9.3:*:*:*:*:postgresql:*:*,
cpe:2.3:a:pgadmin:pgadmin_4:9.4:*:*:*:*:postgresql:*:*,
cpe:2.3:a:pgadmin:pgadmin_4:9.5:*:*:*:*:postgresql:*:*,
cpe:2.3:a:pgadmin:pgadmin_4:9.6:*:*:*:*:postgresql:*:*,
cpe:2.3:a:pgadmin:pgadmin_4:9.7:*:*:*:*:postgresql:*:*,
cpe:2.3:a:pgadmin:pgadmin_4:9.8:*:*:*:*:postgresql:*:*,
cpe:2.3:a:pgadmin:pgadmin_4:9.9:*:*:*:*: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.