Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-102477

Quick assessment

Affected
Eclipse Foundation Eclipse Vert.x
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 Eclipse Vert.x 的以下版本中:[4.0.0, 4.5.34]、[5.0.0, 5.0.12]、[5.1.0, 5.1.9] 或 [5.2.0, 5.2.0],gRPC 端点虽然配置了按消息字节数计算的最大接收大小,但该限制仅作用于接收到的原始字节数(即压缩后的数据)。当处理压缩消息时,该最大尺寸限制仅适用于压缩后的大小,而不适用于解压缩后实际内容的大小。攻击者可以利用这一缺陷,迫使 gRPC 端点分配超出配置所定义大小的内存资源,从而导致端点易受压缩炸弹攻击(compression bomb at

CVSS 8.7 · High EPSS 0.32% · P24

Possible ATT&CK Techniques 1 AI

T1496 · Resource Hijacking

Affected Version Matrix 4

VendorProduct Version RangeStatus
Eclipse Foundation Eclipse Vert.x 4.0.0≤ 4.5.34 affected
5.0.0≤ 5.0.12 affected
5.1.0≤ 5.1.9 affected
5.2.0 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-102477

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: CVE Program / CVE List V5
Vulnerability 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], a gRPC endpoint does have a configurable per message maximum size in bytes, however the maximum size applies to the received bytes. When applied to a compressed message, this only applies to the compressed size and not the actual size of the uncompressed content. This can be used to force a gRPC endpoint to allocate more bytes than the value defined by the configuration, making the endpoint vulnerable to compression bomb attacks. The impacted component is io.vertx:vertx-gprc-server.
Source: CVE Program / CVE List V5
CVSS Information
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
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Eclipse Foundation Eclipse Vert.x 4.0.0 ~ 4.5.34 -

II. Public POCs for CVE-2026-102477

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-102477

请登录查看更多情报信息。

Other References for CVE-2026-102477 (2)

Same Patch Batch · Eclipse Foundation · 2026-10-15 · 25 CVEs total

CVE-2026-19863 9.3 CRITICAL EthereumAuthenticator未授权访问漏洞
CVE-2026-102469 9.2 CRITICAL CVE-2026-102469
CVE-2026-18660 8.8 HIGH Jetty proxy blacklist performs case-sensitive matching of case-insensitive DNS hostnames
CVE-2026-18661 8.8 HIGH Eclipse Jetty 多个版本 Jakarta安全约束绕过漏洞
CVE-2026-102467 8.7 HIGH Vert.x 4.0.0-5.2.0空字节限制致DDoS
CVE-2026-102475 8.7 HIGH Eclipse Vert.x 5.x HTTP代理内存溢出漏洞
CVE-2026-102461 8.7 HIGH Eclipse Vert.x DoS漏洞:JSON Schema验证算法缺陷
CVE-2026-76184 8.2 HIGH Eclipse Jetty HttpClient重定向认证头泄露漏洞
CVE-2026-77711 8.2 HIGH Jetty HttpClient代理凭据泄露漏洞
CVE-2026-102465 8.2 HIGH Vert.x MySQL Client越界数组分配致OOM漏洞
CVE-2026-103224 8.2 HIGH Vert.x MySQL客户端多个版本存在OOM漏洞
CVE-2026-103223 8.2 HIGH Eclipse Vert.x 4-5 PostgreSQL客户端缓冲区溢出致OOM
CVE-2026-102463 8.2 HIGH Eclipse Vertx多版本vertx-pg-client数组解码内存耗尽漏洞
CVE-2026-102464 8.2 HIGH Eclipse Vert.x MQTT未受限存储致OOM
CVE-2026-102466 8.2 HIGH Eclipse Vert.x MySQL客户端拒绝服务漏洞
CVE-2026-102462 8.2 HIGH Vert.x MSSQL Client多个版本OOM漏洞
CVE-2026-76182 6.9 MEDIUM Jetty TryPathsHandler/Filter路径解析逻辑漏洞
CVE-2026-18662 6.9 MEDIUM Jetty安全组件URL模式为空时约束冲突漏洞
CVE-2026-18659 6.9 MEDIUM Unauthenticated authorization bypass in ConstraintSecurityHandler - HTTP method-omission m
CVE-2026-19864 5.6 MEDIUM Eclipse Jetty会话认证凭据明文存储漏洞

Showing top 20 of 25 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2026-102477

No comments yet


Leave a comment