This page was not yet optimized for use on mobile devices.
CVE-2026-32286
Data
| Vulnerability ID | CVE-2026-32286 |
|---|---|
| Published on | 26.03.2026 20:16 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:jackc:pgproto3:2.0.0:alpha1:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgproto3:2.0.0:rc1:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgproto3:2.0.0:rc2:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgproto3:2.0.0:rc3:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgproto3:2.0.1:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgproto3:2.0.2:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgproto3:2.0.3:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgproto3:2.0.4:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgproto3:2.0.5:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgproto3:2.0.6:*:*:*:*:go:*:*,
…
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.