Authenticated code execution via unchecked multibyte lengths
Published Feb 12, 2026 · Updated Feb 12, 2026
Buffer overrun in PostgreSQL allows remote authenticated users to execute arbitrary code on the database server through crafted SQL. Core text routines used pg_mblen() and COPYCHAR without buffer bounds, allowing incomplete multibyte sequences to overrun string buffers. A valid database login and query execution are required; affected releases precede 18.2, 17.8, 16.12, 15.16, and 14.21.
Summary
What happened
Buffer overrun in PostgreSQL allows remote authenticated users to execute arbitrary code on the database server through crafted SQL. Core text routines used pg_mblen() and COPYCHAR without buffer bounds, allowing incomplete multibyte sequences to overrun string buffers. A valid database login and query execution are required; affected releases precede 18.2, 17.8, 16.12, 15.16, and 14.21.
The record
- CVE
- CVE-2026-2006
- Published
- Feb 12, 2026
- Updated
- Feb 12, 2026
- Vendor
- PostgreSQL Global Development Group
- Product
- PostgreSQL
- Classifications
- CWE-129, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2026CVE publishedPublication date reported by the CVE source.
- Feb 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <14.21
- Affected versionversion=15 <15.16
- Affected versionversion=16 <16.12
- Affected versionversion=17 <17.8
- Affected versionversion=18 <18.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo