CVE-2026-18408 Affecting pgvector package, versions <0:0.6.2-2.module+el9.8.0+91036+1d936f05


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.36% (27th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ORACLE9-PGVECTOR-19885481
  • published17 Sept 2026
  • disclosed13 Aug 2026

Introduced: 13 Aug 2026

CVE-2026-18408  (opens in a new tab)

How to fix?

Upgrade Oracle:9 pgvector to version 0:0.6.2-2.module+el9.8.0+91036+1d936f05 or higher.
This issue was patched in ELSA-2026-67491.

NVD Description

Note: Versions mentioned in the description apply only to the upstream pgvector package and not the pgvector package as distributed by Oracle. See How to fix? for Oracle:9 relevant fixed versions and status.

Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql \restrict meta-command input expansion. The fix for CVE-2025-8714 introduced \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. Non-core use of \restrict would be affected, but we've not identified non-core use. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS Base Scores

version 3.1