Eclipse Vert.x up to 4.5.34/5.0.12/5.1.9/5.2.0 vertx-grpc-server allocation of resources

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Eclipse Vert.x up to 4.5.34/5.0.12/5.1.9/5.2.0. The affected element is an unknown function of the component vertx-grpc-server. This manipulation causes allocation of resources. This vulnerability is tracked as CVE-2026-102477. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in Eclipse Vert.x up to 4.5.34/5.0.12/5.1.9/5.2.0 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component vertx-grpc-server. The manipulation with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-102477 since 09/29/2026. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-101937). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Eclipse

Name

• Vert.x

Version

• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4
• 4.5.5
• 4.5.6
• 4.5.7
• 4.5.8
• 4.5.9
• 4.5.10
• 4.5.11
• 4.5.12
• 4.5.13
• 4.5.14
• 4.5.15
• 4.5.16
• 4.5.17
• 4.5.18
• 4.5.19
• 4.5.20
• 4.5.21
• 4.5.22
• 4.5.23
• 4.5.24
• 4.5.25
• 4.5.26
• 4.5.27
• 4.5.28
• 4.5.29
• 4.5.30
• 4.5.31
• 4.5.32
• 4.5.33
• 4.5.34
• 5.0
• 5.0.0
• 5.0.1
• 5.0.2
• 5.0.3
• 5.0.4
• 5.0.5
• 5.0.6
• 5.0.7
• 5.0.8
• 5.0.9
• 5.0.10
• 5.0.11
• 5.0.12
• 5.1
• 5.1.0
• 5.1.1
• 5.1.2
• 5.1.3
• 5.1.4
• 5.1.5
• 5.1.6
• 5.1.7
• 5.1.8
• 5.1.9
• 5.2.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion