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 sizes when processing certain very large inputs, causing memory corruption. An unprivileged database user could potentially run code with the database service account’s operating-system privileges. Applications exposing the affected functions to gigabyte-scale inputs may also permit unauthenticated users to crash the database.

Executive priority

Prioritize prompt remediation because successful exploitation by a low-privileged database user could compromise data and the database host account. Accelerate systems with shared database access or large untrusted application inputs. Emergency treatment is most justified where such exposure exists; active exploitation is not supported by the supplied evidence.

Technical view

Integer wraparound in multiple PostgreSQL features can produce undersized allocations followed by out-of-bounds writes. The issue affects releases before 18.4, 17.10, 16.14, 15.18, and 14.23. CVSS 3.1 rates it 8.8 because exploitation requires low database privileges but could compromise confidentiality, integrity, and availability without user interaction.

Likely exposure

Highest exposure exists where untrusted users hold PostgreSQL accounts or applications pass gigabyte-scale untrusted inputs into relevant database functions. Internet reachability alone does not establish exploitability. The supplied sources do not identify the specific functions, so application-level exposure requires vendor guidance and workload review.

Exploitation context

The source bundle does not establish active exploitation, and the CVE is not listed as KEV. It describes potential arbitrary code execution for an unprivileged database user. An application input provider may cause a segmentation fault when an application forwards gigabyte-scale inputs, but code execution through that path is not established.

Researcher notes

The bundle attributes the flaw to CWE-190 and multiple server features but does not name affected functions or provide technical trigger details. Avoid assuming every network client can reach the vulnerable path. Validate function-level exposure using PostgreSQL’s advisory and downstream vendor documentation. Vendor backports may fix the issue without matching upstream release numbers.

Mitigation direction

  • Upgrade to PostgreSQL 18.4, 17.10, 16.14, 15.18, or 14.23, as applicable.
  • For vendor-packaged PostgreSQL, apply the corresponding supported vendor security update or backport.
  • Restrict unnecessary database accounts and privileges until updates are complete.
  • Limit untrusted gigabyte-scale application inputs reaching database functions where operationally feasible.
  • Review PostgreSQL and operating-system service-account activity for unexpected behavior.

Validation and detection

  • Inventory PostgreSQL major and minor versions across production, replicas, development, and managed services.
  • Confirm each installation meets or exceeds the fixed release for its major version.
  • Check vendor package advisories where version strings reflect backported fixes.
  • Identify applications that pass very large untrusted values into PostgreSQL functions.
  • Verify unnecessary database users and privileges have been removed or restricted.
  • After updating, confirm service health, replication, and application database operations.
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-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
37Source 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