LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2006: PostgreSQL missing validation of multibyte character length executes arbitrary code

Missing validation of multibyte character length in PostgreSQL text manipulation allows a database user to issue crafted queries that achieve a buffer overrun. That suffices to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

PostgreSQL can mishandle certain multibyte text operations, allowing an authenticated database user to crash through memory safety boundaries and potentially run code as the database operating-system account. This is serious for any PostgreSQL system where users, tenants, applications, or extensions can submit database queries.

Executive priority

Treat this as a high-priority database patching issue. It can move from database access to operating-system code execution as the database service user, which raises confidentiality, integrity, and availability risk for affected data platforms.

Technical view

The issue is missing validation of multibyte character length in PostgreSQL text manipulation. Crafted queries can trigger a buffer overrun and arbitrary code execution under the database server OS user. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are listed as affected.

Likely exposure

Exposure is most likely where affected PostgreSQL versions are reachable by application accounts, database users, tenants, analytics users, or other principals allowed to run SQL. The source bundle does not identify a specific deployment configuration beyond vulnerable PostgreSQL versions.

Exploitation context

The CVSS vector indicates network reachability, low attack complexity, low privileges required, and no user interaction. The bundle marks KEV as false and provides no cited evidence of active exploitation, so active exploitation should not be assumed.

Researcher notes

Key constraints are authenticated database access and vulnerable text manipulation handling. The provided sources do not include proof-of-concept details, detection logic, or active exploitation claims. Avoid assuming product exposure beyond PostgreSQL and distribution packages named by PostgreSQL or Red Hat.

Mitigation direction

  • Upgrade PostgreSQL to 18.2, 17.8, 16.12, 15.16, 14.21, or later.
  • Apply relevant Red Hat security errata for Red Hat-packaged PostgreSQL deployments.
  • Prioritize systems accepting SQL from less-trusted users, tenants, or exposed applications.
  • Check PostgreSQL and OS vendor guidance for distribution-specific fixed package versions.
  • Limit unnecessary database privileges while patching is scheduled.

Validation and detection

  • Inventory PostgreSQL major and minor versions across production and non-production systems.
  • Confirm every instance is at or above the fixed version for its major release.
  • Map which application or human accounts can issue SQL to affected instances.
  • Review vendor package advisories for Red Hat systems before closing remediation.
  • Confirm vulnerability scanner findings against actual PostgreSQL package and server versions.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1285: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-129: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2006 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
35Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9PostgreSQL
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-2006Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPpostgresql: PostgreSQL missing validation of multibyte character length executes arbitrary code
other:Red Hat severity ratingcvssV3_1
  • 2026-02-12T14:01:27.485Z: Reported to Red Hat.
  • 2026-02-12T13:00:10.490Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aPostgreSQL18, 17, 16, 15, 0unaffected
Weakness

CWE details

CWE-1285CWE-129

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.