{
  "id": "CVE-2026-100665",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-100665",
  "published_at": "2026-09-26T13:23:31.242Z",
  "title": "Netty 4.2.11 through 4.2.17 QUIC Hostname Verification Bypass",
  "vendor": "netty",
  "product": "netty",
  "cvss": {
    "score": 8.7,
    "source": "cna",
    "vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "Netty versions from 4.2.11.Final before 4.2.18.Final contain an incomplete hostname verification fix in the QUIC certificate verification path when using a plain X509TrustManager. The BoringSSLCertificateVerifyCallback discards the SSLEngine for plain trust managers, preventing endpoint identification from running even when HTTPS verification is configured. Attackers on the network path can present a certificate chain for the wrong hostname that the plain trust manager accepts, bypassing hostname authentication for QUIC clients.",
  "cwe": "CWE-295",
  "cvss_by_source": {
    "cna": 8.7
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "netty",
        "product": "netty",
        "ranges": [
          "\u003e= 4.2.11.Final, \u003c 4.2.18.Final"
        ],
        "fixed_in": [
          "4.2.18.Final"
        ]
      }
    ],
    "upgrade": [
      "Upgrade netty to 4.2.18.Final or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/netty/netty/security/advisories/GHSA-mj35-3qqm-q387"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/netty/netty/commit/09e72c4fd8007277121ed48db63a124b112b96fe"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/netty/netty/commit/994e887ed9"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
