← back to feed
CVE-2026-102465

CVE-2026-102465

waiting for further signalsZero needs more public information before it can validate it.

GHSA-2fhm-447p-jh2m ↗EUVD-2026-101927 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Eclipse Foundation Eclipse Vert.x 5.2.0; >=5.0.0, <=5.1.8; <=4.5.34
fixed in 5.2.1, 5.1.10, 4.5.35
ETK-2026-1775Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:maven/vertx-redis-client
cvss8.2cna vendorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
5d 05h 20msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+29h10m
0
+2h
+4h
+6h
+8h
+10h

description

Eclipse Vert.x releases 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 an unbounded allocation issue in the Redis RESP parser. A malicious Redis server or an on-path attacker can exhaust application memory and disrupt workloads sharing the affected event loop.

mitigation

Upgrade vertx-redis-client to 5.2.1; vertx-redis-client to 5.1.10; vertx-redis-client to 4.5.35 or later.

fixed in 5.2.1, 5.1.10, 4.5.35

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.21%10th percentile
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 07:27Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

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.

  1. 2026-10-15 07:27Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-102465

this entry in the feed

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

{
  "etk_id": "ETK-2026-1775",
  "cve_id": "CVE-2026-102465",
  "display_id": "CVE-2026-102465",
  "ghsa_id": "GHSA-2fhm-447p-jh2m",
  "euvd_id": "EUVD-2026-101927",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unbounded RESP array allocation in Eclipse Vert.x Redis client",
  "summary": "Eclipse Vert.x releases 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 an unbounded allocation issue in the Redis RESP parser. A malicious Redis server or an on-path attacker can exhaust application memory and disrupt workloads sharing the affected event loop.",
  "mitigation": "Upgrade vertx-redis-client to 5.2.1; vertx-redis-client to 5.1.10; vertx-redis-client to 4.5.35 or later.",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse Vert.x",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "5.2.0"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "5.2.1"
      ],
      "package_name": "vertx-redis-client",
      "purl": "pkg:maven/vertx-redis-client"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">=5.0.0, <=5.1.8"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "5.1.10"
      ],
      "package_name": "vertx-redis-client",
      "purl": "pkg:maven/vertx-redis-client"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "<=4.5.34"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "4.5.35"
      ],
      "package_name": "vertx-redis-client",
      "purl": "pkg:maven/vertx-redis-client"
    }
  ],
  "cwes": null,
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0021,
  "epss_percentile": 0.1053,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.138337416666666,
  "t0_at": "2026-10-15T07:27:55.055000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T07:27:55.055000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T07:27:55.055000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-102465"
    }
  }
}

published 2026-10-16 12:21Z
last change 2026-10-21 17:00Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.