CVE-2026-102467

waiting for further signals

GHSA-h722-h6c2-6j3c ↗EUVD-2026-101929 ↗

no check availablenot proven exploitable

cve.orgpublic pockev

Eclipse Foundation Eclipse Vert.x >= 5.0.0, <= 5.1.8; 5.2.0; >= 4.0.0, <= 4.5.34

fixed in 5.1.10, 5.2.1, 4.5.35

ETK-2026-1655, permanent identifier

pkg:maven/io.vertx/vertx-core

cvss8.7cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

6d 12h 04msince last run

30mAI analysis

timeline

0 = cve.org publication

trigger signal −7.4dcve.org publicationwaiting for further signals+0.1d

−6d

−4d

−2d

description

Vert.x core WebSocket processing is affected in the listed 4.x, 5.0.x, 5.1.x, and 5.2.0 releases. An attacker able to send compressed WebSocket traffic can consume excessive memory and cause denial of service.

mitigation

Upgrade io.vertx:vertx-core to 5.1.10; io.vertx:vertx-core to 5.2.1; io.vertx:vertx-core to 4.5.35 or later.

fixed in 5.1.10, 5.2.1, 4.5.35

check

exploit

automation

contextual

auth required

EPSS

0.26%16th percentile

agent run time

30m

cve.org record, t = 0

2026-10-15 07:19Z

Δ to public poc

–

Δ to kev

–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

2026-10-07 21:55Z
ghsa: trigger signal
https://github.com/eclipse-vertx/vert.x/security/advisories/GHSA-h722-h6c2-6j3c
2026-10-15 07:19Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-102467

this entry in the feed

GET /api/v1/feed/CVE-2026-102467

{
  "etk_id": "ETK-2026-1655",
  "cve_id": "CVE-2026-102467",
  "display_id": "CVE-2026-102467",
  "ghsa_id": "GHSA-h722-h6c2-6j3c",
  "euvd_id": "EUVD-2026-101929",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unbounded WebSocket decompression in Vert.x",
  "summary": "Vert.x core WebSocket processing is affected in the listed 4.x, 5.0.x, 5.1.x, and 5.2.0 releases. An attacker able to send compressed WebSocket traffic can consume excessive memory and cause denial of service.",
  "mitigation": "Upgrade io.vertx:vertx-core to 5.1.10; io.vertx:vertx-core to 5.2.1; io.vertx:vertx-core to 4.5.35 or later.",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse Vert.x",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 5.0.0, <= 5.1.8"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "5.1.10"
      ],
      "package_name": "io.vertx:vertx-core",
      "purl": "pkg:maven/io.vertx/vertx-core"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "5.2.0"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "5.2.1"
      ],
      "package_name": "io.vertx:vertx-core",
      "purl": "pkg:maven/io.vertx/vertx-core"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0, <= 4.5.34"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "4.5.35"
      ],
      "package_name": "io.vertx:vertx-core",
      "purl": "pkg:maven/io.vertx/vertx-core"
    }
  ],
  "cwes": null,
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_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",
  "epss_score": 0.0026,
  "epss_percentile": 0.1651,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 29.795367816666666,
  "t0_at": "2026-10-15T07:19:57.248000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T21:55:53+00:00",
      "days": -7.3917158333333335,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T07:19:57.248000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-102467"
    }
  }
}

published 2026-10-15 08:17Z
last change 2026-10-21 20:26Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.