Update dependency io.vertx:vertx-core to v4.5.27 [SECURITY] (main)#40
Draft
renovatebot-confluentinc[bot] wants to merge 1 commit into
Draft
Conversation
renovatebot-confluentinc
Bot
force-pushed
the
renovate/main-maven-io.vertx-vertx-core-vulnerability
branch
from
782110d to
a6aa02d
Compare
renovatebot-confluentinc
Bot
changed the title
renovatebot-confluentinc
Bot
force-pushed
the
renovate/main-maven-io.vertx-vertx-core-vulnerability
branch
from
a6aa02d to
70ef79f
Compare
renovatebot-confluentinc
Bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For any questions/concerns about this PR, please review the Renovate Bot wiki/FAQs, or the #renovatebot Slack channel.
This PR contains the following updates:
4.5.13→4.5.27Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Vert.x Web static handler component cache can be manipulated to deny the access to static files
CVE-2026-1002 / GHSA-cphf-4846-3xx9
More information
Details
The Vert.x Web static handler component cache can be manipulated to deny the access to static files served by the handler using specifically crafted request URI.
The issue comes from an improper implementation of the C. rule of section 5.2.4 of RFC3986 and is fixed in Vert.x Core component (used by Vert.x Web): https://github.com/eclipse-vertx/vert.x/pull/5895
Steps to reproduce
Given a file served by the static handler, craft an URI that introduces a string like bar%2F..%2F after the last / char to deny the access to the URI with an HTTP 404 response. For example https://example.com/foo/index.html can be denied with https://example.com/foo/bar%2F..%2Findex.html
Mitgation
Disabling Static Handler cache fixes the issue.
StaticHandler staticHandler = StaticHandler.create().setCachingEnabled(false);
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Vert.x has a DoS via unbounded server-side SNI SslContext cache growth
CVE-2026-6860 / GHSA-3g76-f9xq-8vp6
More information
Details
Potential unbounded server-side SNI
SslContextcache growth in Vert.x TLS handling, with = resource-exhaustion / DoS impact. On affected versions, matching server-side SNI names are cached viacomputeIfAbsent(serverName, ...)in a serverName-keyedSslContextcache.The implementation differs slightly by branch, but the same sink appears to be present in released versions
4.3.4through5.0.11:4.3.x:SSLHelper4.4.x/4.5.x:SslChannelProvider5.0.xand currentmaster:SslContextProviderWhen server-side SNI is enabled and wildcard or otherwise broad hostname mappings are used, an unauthenticated client can send many distinct matching SNI names and cause the server to retain increasing numbers of
SslContextentries over time, leading to increasing memory consumption and possible DoS conditions.Steps to reproduce
setSsl(true)andsetSni(true).What are the affected versions?
Affected released versions confirmed on
origin:4.3.4through4.3.84.4.0through4.4.94.5.0through4.5.265.0.0through5.0.11Not affected by the same sink:
4.0.xthrough4.2.x4.3.0through4.3.3Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Vert.x Web static handler component cache can be manipulated to deny the access to static files
CVE-2026-1002 / GHSA-cphf-4846-3xx9
More information
Details
The Vert.x Web static handler component cache can be manipulated to deny the access to static files served by the handler using specifically crafted request URI.
The issue comes from an improper implementation of the C. rule of section 5.2.4 of RFC3986 and is fixed in Vert.x Core component (used by Vert.x Web): https://github.com/eclipse-vertx/vert.x/pull/5895
Steps to reproduce
Given a file served by the static handler, craft an URI that introduces a string like bar%2F..%2F after the last / char to deny the access to the URI with an HTTP 404 response. For example https://example.com/foo/index.html can be denied with https://example.com/foo/bar%2F..%2Findex.html
Mitgation
Disabling Static Handler cache fixes the issue.
StaticHandler staticHandler = StaticHandler.create().setCachingEnabled(false);
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Vert.x has a DoS via unbounded server-side SNI SslContext cache growth
CVE-2026-6860 / GHSA-3g76-f9xq-8vp6
More information
Details
Potential unbounded server-side SNI
SslContextcache growth in Vert.x TLS handling, with = resource-exhaustion / DoS impact. On affected versions, matching server-side SNI names are cached viacomputeIfAbsent(serverName, ...)in a serverName-keyedSslContextcache.The implementation differs slightly by branch, but the same sink appears to be present in released versions
4.3.4through5.0.11:4.3.x:SSLHelper4.4.x/4.5.x:SslChannelProvider5.0.xand currentmaster:SslContextProviderWhen server-side SNI is enabled and wildcard or otherwise broad hostname mappings are used, an unauthenticated client can send many distinct matching SNI names and cause the server to retain increasing numbers of
SslContextentries over time, leading to increasing memory consumption and possible DoS conditions.Steps to reproduce
setSsl(true)andsetSni(true).What are the affected versions?
Affected released versions confirmed on
origin:4.3.4through4.3.84.4.0through4.4.94.5.0through4.5.265.0.0through5.0.11Not affected by the same sink:
4.0.xthrough4.2.x4.3.0through4.3.3Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.