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 PostgreSQL message decoder reads the 4-byte… (CVE-2026-103223)
Description
Eclipse Vert.x versions 4.0.0 through 4.5.34, 5.0.0 through 5.0.12, 5.1.0 through 5.1.9, and 5.2.0 have a vulnerability in the PostgreSQL message decoder. The decoder reads the 4-byte message length field from the PostgreSQL wire protocol without validating its maximum size. A malicious or compromised PostgreSQL server can send a message with an extremely large length value, causing unbounded memory allocation on the client and potentially leading to an out-of-memory crash. This occurs before authentication completes.
CVSS v3.1
Score 5.9medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Eclipse Vert.x's PostgreSQL client (io.vertx:vertx-pg-client) involves improper validation of the 4-byte message length field in the PostgreSQL wire protocol. The decoder accepts a length field up to Integer.MAX_VALUE without any maximum size check. A malicious or compromised PostgreSQL server or man-in-the-middle attacker can exploit this by sending a message header with a very large length value, causing the client to allocate memory without bounds. This leads to unbounded memory consumption and can cause the client application to crash due to out-of-memory errors. The issue affects multiple version ranges of Eclipse Vert.x as specified.
Potential Impact
The vulnerability can cause a denial of service on the client side by exhausting memory resources, leading to an out-of-memory crash. There is no impact on confidentiality or integrity as per the CVSS vector. The attack can be triggered before authentication, meaning it can be exploited without valid credentials if the client connects to a malicious or compromised PostgreSQL server or if a man-in-the-middle attack is possible.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid connecting to untrusted PostgreSQL servers and ensure network protections against man-in-the-middle attacks are in place. Monitor for vendor updates and apply official patches once released.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-h6w8-ffgq-ghpg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-103223"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ad7ec262cdf04f6566b00a7
Added to database: 10/20/2026, 22:33:10 UTC
Last enriched: 10/20/2026, 22:33:22 UTC
Last updated: 10/20/2026, 22:33:22 UTC
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.