This page was not yet optimized for use on mobile devices.
CVE-2026-33815
Data
| Vulnerability ID | CVE-2026-33815 |
|---|---|
| Published on | 07.04.2026 16:16 |
| Severity | CRITICAL |
Vulnerable configurations
-
cpe:2.3:a:jackc:pgx:-:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgx:2.0.0:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgx:2.1.0:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgx:2.2.0:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgx:2.3.0:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgx:2.4.0:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgx:2.5.0:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgx:2.6.0:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgx:2.7.0:*:*:*:*:go:*:*,
cpe:2.3:a:jackc:pgx:2.7.1:*:*:*:*: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.