On November 12, 2026, PostgreSQL released 18.7, 17.12, 16.16, 15.20 and 14.25, fixing 52 CVEs (38 High, 14 Medium/Low, none Critical). PostgreSQL 14 is now end of life.
Risk to OPSWAT Products: Low
- Bundled databases are not reachable from outside the host or cluster by default.
- OPSWAT products do not use the affected optional components: PL/Perl, PL/Tcl, dblink, logical replication, foreign data wrappers.
- The core server CVEs require an attacker who can already log in to the database and run SQL.
- Not affected: Other products than the ones below are not affected.
Fixed Releases
Product | Bundled Today | Fixed Release | Available | Interim Fix |
MetaDefender Core | 18.x | 5.24.1 (PG 18.7) | Nov 18 | — |
MetaDefender Cluster | 18.x | 2.11 (PG 18.7) | Nov 18 | — |
MetaDefender ICAP Server | 16.15 | 5.16.2 (PG 16.16) | Nov 18 | — |
MetaDefender Storage Security | 17.x | 4.6.2 (PG 17.12) | Nov 16 | Yes |
MetaDefender Software Supply Chain | 17.x | 4.3.1 (PG 17.12) | Nov 16 | Yes |
MetaDefender Email Gateway Security | 14.x | 6.4.4 (PG 18.7) | Nov 30 | — |
What to Do
- Embedded database: upgrade to the fixed release above.
- Remote database: apply the latest minor release of your branch (18.7, 17.12, 16.16 or 15.20). Check supported versions in each product’s documentation. Minor upgrades need no dump, restore or pg_upgrade. If you run PG 14, plan a major upgrade.
- Until then: keep the PostgreSQL port closed to the network, limit server access to administrators, and keep database credentials private.
- Vulnerability scanners will flag the bundled PostgreSQL version until you update.
Interim Update (Optional, Before the Fixed Release)
- Storage Security, Linux: mdss -u update · Helm: set postgres-mdss.image=postgres:17.12 · Air-gapped: docker load the 17.12 image, then mdss -c restart
- Software Supply Chain, Linux: add POSTGRES_TAG=17.12 to /etc/mdssc/customer.env, then sudo mdssc -u update · Helm: --set mdssc_components.postgres-mdssc.image=postgres:17.12
- Both keep existing data (minor upgrade within PG 17).
Appendix: CVE-by-CVE Review (Core, Cluster)
Area | High CVEs | Why MetaDefender Core is not exposed |
PL/Perl, PL/Tcl | CVE-2026-116307, -116309, -116319, -116320, -116323, -116326 | These languages are not installed. |
pg_restore, reindexdb, vacuumdb --missing-stats-only, pg_dump tar format | CVE-2026-116313, -116314, -116325, -116330 | These tools and options are not used. |
Logical replication, foreign data wrappers | CVE-2026-120145, -120149 | These features are not used. |
Third-party extension scripts | CVE-2026-120153 | Only extensions shipped with PostgreSQL are used. |
Core server code execution | CVE-2026-6460, -18447, -116304, -116306, -116316, -116328, -116329, -116331, -116332, -116335, -116336, -120139, -120141, -120142, -120143, -120144, -120148, -120150, -120151 | An attacker would need to log in to the database and run their own SQL. |
Text search functions | CVE-2026-116315, -116317 | These functions are not called. |
dblink | CVE-2026-14661, -120147 | dblink is not used during operation. |
CREATE EXTENSION, pg_dump constraint names | CVE-2026-6467, -116318 | An attacker would first need to create objects in the database. |
Questions: security.incident@opswat.com
