Quick answers
- Is CVE-2026-6467 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6467 being exploited in the wild.
- How severe is CVE-2026-6467?
- High severity, with a CVSS score of 7.2, published 12 November 2026.
- Which products and versions are affected?
- PostgreSQL before 18.7, 17.12, 16.16, 15.20, and 14.25.
- Is there a fix for CVE-2026-6467?
- Yes: fixed in PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-6467 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-6467?
- Check whether you run PostgreSQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25
Technical details
The vulnerability exists in PostgreSQL's extension installation mechanism via CREATE EXTENSION, ALTER SCHEMA, and ALTER EXTENSION commands. An attacker with database-level CREATE privilege can manipulate the search path using ALTER SCHEMA ... RENAME or CREATE EXTENSION ... SCHEMA "$user" to cause trusted extension scripts to locate and execute arbitrary SQL code as the bootstrap superuser. The flaw arises from uncontrolled search path elements allowing schema name resolution to be redirected to attacker-controlled objects.
Affected products
- PostgreSQL PostgreSQL before 18.7, 17.12, 16.16, 15.20, and 14.25
Timeline
- 2026-11-12: disclosed
- 2026-11-12: patched