Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-6860 medium CVSS 5.3

Vulnerability in io.vertx:vertx-core (CVE-2026-6860)

Summary

Vulnerability in io.vertx:vertx-core (CVE-2026-6860). Risk of unauthorized operations or information disclosure. Exploitable via SslContext. Mitigation: upgrade to 5.0.12 or later.

Original description

The description as published by the source.

Potential unbounded server-side SNI SslContext cache growth in Vert.x TLS handling, with = resource-exhaustion / DoS impact. On affected versions, matching server-side SNI names are cached via computeIfAbsent(serverName, ...) in a serverName-keyed SslContext cache.

The implementation differs slightly by branch, but the same sink appears to be present in released versions 4.3.4 through 5.0.11:

  • 4.3.x: SSLHelper
  • 4.4.x / 4.5.x: SslChannelProvider
  • 5.0.x and current master: SslContextProvider

When 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 SslContext entries over time, leading to increasing memory consumption and possible DoS conditions.

Steps to reproduce

  1. Configure a Vert.x server with setSsl(true) and setSni(true).
  2. Use a keystore or mapping where many distinct SNI names match a wildcard or similarly broad rule.
  3. Send repeated connections with distinct matching SNI values.
  4. Observe that the SNI cache size grows with the number of unique matching names.

What are the affected versions?

Affected released versions confirmed on origin:

  • 4.3.4 through 4.3.8
  • 4.4.0 through 4.4.9
  • 4.5.0 through 4.5.26
  • 5.0.0 through 5.0.11

Not affected by the same sink:

  • 4.0.x through 4.2.x
  • 4.3.0 through 4.3.3

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-6860 has been found in io.vertx:vertx-core.
Attackers can target a specific entry point like SslContext over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade io.vertx:vertx-core to 5.0.12 or later.
If unsure, ask your IT team or search "io.vertx:vertx-core CVE-2026-6860" on the vendor's site.

CVE-2026-6860 (io.vertx:vertx-core) — CWE-295 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: SslContext / SSLHelper / SslChannelProvider / master
Patched: 5.0.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-295) exists in io.vertx:vertx-core. Attackers reach the vulnerable code path via SslContext without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of io.vertx:vertx-core. Attack surface: SslContext / SSLHelper / SslChannelProvider / master.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.0.12.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.vertx:vertx-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade io.vertx:vertx-core to 5.0.12

    ステージング環境で 5.0.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven io.vertx:vertx-core
[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"fixed":"5.0.12"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details