Is CVE-2026-120148 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-120148 being exploited in the wild.

How severe is CVE-2026-120148?

High severity, with a CVSS score of 8.1, published 12 November 2026.

Which products and versions are affected?

PostgreSQL Before 14.25, 15.20, 16.16, 17.12, and 18.7.

Is there a fix for CVE-2026-120148?

Yes: fixed in PostgreSQL 14.25, 15.20, 16.16, 17.12, 18.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-120148 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-120148?

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.

CVE-2026-120148: PostgreSQL extended statistics type confusion arbitrary code execution

CVE-2026-120148 · Severity: high · CVSS 8.1 · Published 2026-11-12

PostgreSQL is a widely-used open-source database system. A type confusion vulnerability in its extended statistics feature allows an authenticated database user to execute arbitrary code with the privileges of the operating system user running the database server, potentially leading to complete system compromise.

Quick answers

Is CVE-2026-120148 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-120148 being exploited in the wild.
How severe is CVE-2026-120148?: High severity, with a CVSS score of 8.1, published 12 November 2026.
Which products and versions are affected?: PostgreSQL Before 14.25, 15.20, 16.16, 17.12, and 18.7.
Is there a fix for CVE-2026-120148?: Yes: fixed in PostgreSQL 14.25, 15.20, 16.16, 17.12, 18.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-120148 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-120148?: 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 14.25, 15.20, 16.16, 17.12, 18.7

Technical details

A type confusion flaw in PostgreSQL's extended statistics handling occurs when processing an anonymous RECORD type in a statistics expression whose backend-local type identifier refers to a different row type in another session. The vulnerability requires database authentication and user interaction to create malicious statistics objects, but allows arbitrary code execution at the OS level with database server privileges.

Affected products

PostgreSQL Before 14.25, 15.20, 16.16, 17.12, and 18.7

Timeline

2026-11-12: disclosed
2026-11-12: patched

References

https://www.postgresql.org/support/security/CVE-2026-120148/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.