LiveActive security incident?Get immediate response
CVE Record

CVE-2026-6473: PostgreSQL server undersizes allocations, via integer wraparound

Integer wraparound in multiple PostgreSQL server features allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds. This may execute arbitrary code as the operating system user running the database. In applications that pass gigabyte-scale user inputs to the relevant database functions, the application input provider may achieve a segmentation fault. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 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 miscalculate memory allocation sizes when processing very large inputs, leading to memory corruption. A low-privilege database user could potentially run code with the database service account’s operating-system permissions. Applications passing gigabyte-scale untrusted inputs may also expose the server to crashes.

Executive priority

Treat this as a high-priority patching issue because authenticated low-privilege access may become host-level code execution under the database service account. Prioritize internet-reachable systems, shared databases, and applications accepting exceptionally large untrusted inputs. Escalate immediately if suspicious crashes or unexpected database-account processes appear.

Technical view

Integer wraparound in multiple PostgreSQL server features can produce undersized allocations followed by out-of-bounds writes. The issue is CWE-190 and carries CVSS 3.1 score 8.8. A successful attack may cause a segmentation fault or arbitrary code execution as the operating-system user running PostgreSQL.

Likely exposure

Affected deployments run PostgreSQL versions before 18.4, 17.10, 16.14, 15.18, or 14.23. Risk is greatest where untrusted users have database credentials or applications forward gigabyte-scale user-controlled inputs to affected database functions. The supplied sources do not identify the specific functions.

Exploitation context

The CVSS vector indicates network reachability, low complexity, required low privileges, and no user interaction. The supplied record is not listed in KEV, and the provided sources do not establish active exploitation. This absence should not be interpreted as proof that exploitation is impossible.

Researcher notes

The bundle identifies multiple affected server features but does not name them, so function-level exposure cannot be confirmed here. Assessment should focus on version status, authentication boundaries, large-input data flows, crash evidence, and vendor advisories. Avoid concluding compromise solely from a segmentation fault because the source describes crashes as one possible outcome.

Mitigation direction

  • Upgrade to PostgreSQL 18.4, 17.10, 16.14, 15.18, 14.23, or a later supported release.
  • Apply the relevant operating-system vendor security update when PostgreSQL is distribution-managed.
  • Restrict database accounts and network access to trusted users while updates are pending.
  • Limit or reject gigabyte-scale untrusted application inputs before affected database processing.

Validation and detection

  • Record each PostgreSQL server’s exact runtime version and package provenance.
  • Confirm every supported major release meets or exceeds its stated fixed minor version.
  • Identify low-privilege database accounts accessible by untrusted or external parties.
  • Review applications for user-controlled, gigabyte-scale inputs passed into database functions.
  • Verify vendor packages are installed and PostgreSQL services restarted where the update requires it.
Prepared
Confidence
high
Sources
5

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-190: 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-6473 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
39Source 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-6473Attack 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: integer overflow can cause an undersized allocation and an out-of-bounds write
other:Red Hat severity ratingcvssV3_1
  • 2026-05-14T14:01:48.197Z: Reported to Red Hat.
  • 2026-05-14T13:00:09.446Z: 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-190

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

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs