Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-116542medium6.9

Netty netty-tcnative before 2.0.84.Final SNI Hostname Spoofing via Modified UTF-8 Decoding

Impact

Netty netty-tcnative before 2.0.84.Final has an SNI hostname spoofing vulnerability, allowing remote unauthenticated clients to alter hostnames via modified UTF-8 decoding. Attackers can send overlong encodings to confuse SNI-based certificate selection and access decisions.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

netty · VulnCheck

netty-tcnative

1 range

Package identity

pkg:maven/io.netty/netty-tcnativeExplore io.netty:netty-tcnative →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 2.0.84.Final

custom versions

unaffected

unknown

Other versions: unaffected

netty · VulnCheck

netty-tcnative-boringssl-static

1 range

Package identity

pkg:maven/io.netty/netty-tcnative-boringssl-staticExplore io.netty:netty-tcnative-boringssl-static →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 2.0.84.Final

custom versions

unaffected

unknown

Other versions: unaffected

Original source description

Netty netty-tcnative before 2.0.84.Final contains an SNI hostname spoofing vulnerability that allows remote unauthenticated clients to alter hostnames via JNI NewStringUTF decoding. Attackers can send overlong encodings like 0xC0 0x80 in the ClientHello server_name to confuse SNI-based certificate selection, access decisions, and logging.

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-116542

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-176 ↗

Improper Handling of Unicode Encoding

VulnCheck

Related →
Contributing organizations · 2
VulnCheck

Assigning organization

2026-10-26
CISA-ADP

Additional data publisher

2026-10-31

What changed

Follow changes
  1. CVE · CVE-2026-116542

    Observed 2026-10-31T01:58:03.924Z · upstream updated 2026-10-31T01:27:08.152Z

    Prioritization updated

    before

    []

    after

    [
      {
        "source": "CISA-ADP",
        "type": "SSVC",
        "role": "CISA Coordinator",
        "timestamp": "2026-10-31T01:26:42.450861Z",
        "decisions": [
          {
            "name": "Exploitation",
            "value": "poc"
          },
          {
            "name": "Automatable",
            "value": "yes"
          },
          {
            "name": "Technical Impact",
            "value": "partial"
          }
        ]
      }
    ]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.

References

6 sources