| RHSA-2026:59278 |
2026-08-25 |
Important |
PostgreSQL |
8 |
CVE-2026-42198 |
postgresql-jdbc security update |
| RHSA-2026:59277 |
2026-08-25 |
Important |
PostgreSQL |
8 |
CVE-2026-42198 |
postgresql-jdbc security update |
| RHSA-2026:54532 |
2026-08-13 |
Important |
PostgreSQL |
9 |
CVE-2026-42198 |
postgresql-jdbc security update |
| RHSA-2026:52978 |
2026-08-10 |
Important |
PostgreSQL |
8 |
CVE-2026-42198 |
postgresql-jdbc security update |
| RHSA-2026:52930 |
2026-08-10 |
Important |
PostgreSQL |
9 |
CVE-2026-42198 |
postgresql-jdbc security update |
| RHSA-2026:52929 |
2026-08-10 |
Important |
PostgreSQL |
9 |
CVE-2026-42198 |
postgresql-jdbc security update |
| RHSA-2026:52928 |
2026-08-10 |
Important |
PostgreSQL |
10 |
CVE-2026-42198 |
postgresql-jdbc security update |
| RHSA-2026:25030 |
2026-06-10 |
Important |
PostgreSQL |
8 |
CVE-2026-42198 |
postgresql-jdbc security update |
| RHSA-2026:24348 |
2026-06-08 |
Important |
PostgreSQL |
10 |
CVE-2026-42198 |
postgresql-jdbc security update |
| RHSA-2026:22304 |
2026-06-01 |
Important |
PostgreSQL |
9 |
CVE-2026-42198 |
postgresql-jdbc security update |