CVE-2026-102463

Vulnerability record

  • High 8.2

Description

In Eclipse Vert.x versions [4.0.0, 4.5.34] or [5.0.0,5.0.12] or [5.1.0,5.1.9] or [5.2.0, 5.2.0], the binary array decoder in vertx-pg-client (DataTypeCodec.binaryDecodeArray) allocates a Java array sized by a server-declared 32-bit dimension count with no upper bound. A malicious or compromised PostgreSQL server, or an on-path attacker intercepting an unencrypted connection, can send a crafted DataRow message with an excessively large array dimension value, causing the client to attempt a multi-gigabyte heap allocation and crash with an OutOfMemoryError. The impacted component is io.vertx:vertx-pg-client.

Key facts

Published
15 Oct 2026
Last changed
15 Oct 2026
Assigned by
eclipse
EPSS
0.306% likely to be exploited in the next 30 days, higher than 23.737% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.2CVSS 4.0, Highfrom the CNA (eclipse)CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Eclipse FoundationEclipse Vert.x
  • Default status: unaffected
  • 4.0.0 up to and including 4.5.34 (affected)
  • 5.0.0 up to and including 5.0.12 (affected)
  • 5.1.0 up to and including 5.1.9 (affected)
  • 5.2.0 (affected)

Timeline

  1. 15 Oct 2026 Published

Weakness

References