Approved changes feed: RSS · Atom

cpe:2.3:a:eclipse_foundation:eclipse_vert.x:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorEclipse Foundation (2c315c48-0111-5572-bbde-cc70cfafb2e9)
ProductEclipse Vert.X (f92f0d42-3d0a-54f7-bd44-91e3edf76478)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-6860 vulnerable 2026-06-03 15:27:55.811801 Details available
A TCP client can perform a TLS handshake and present the server name extension with a server name that is accepted by a server wildcard name, e.g. if the server is configured with a certificate accepting *.example.com, any XYZ.example.com where xyz is a valid name can be used.
Published: 2026-05-06T09:55:12.531Z
Updated: 2026-05-12T20:29:09.712Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-8391 vulnerable 2026-06-03 14:58:18.326482 Eclipse Vert.x gRPC server does not limit the maximum message size
In Eclipse Vert.x version 4.3.0 to 4.5.9, the gRPC server does not limit the maximum length of message payload (Maven GAV: io.vertx:vertx-grpc-server and io.vertx:vertx-grpc-client).  This is fixed in the 4.5.10 version.  Note this does not affect the Vert.x gRPC server based grpc-java and Netty libraries (Maven GAV: io.vertx:vertx-grpc)
Published: 2024-09-04T15:27:58.478Z
Updated: 2024-09-04T17:40:20.318Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.