ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-32283

If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources.

Published Apr 8, 2026 · catalog updated Sep 18, 2026 · If one side of

Check if you run it

No confirmed exploitation is on record for CVE-2026-32283. EPSS is 0.62%. Act only if a listed version of If one side of is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (If one side of).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.62%
Remediation
Advisory link
Affected products
cpe golang/go

If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe golang/goversion unspecified

How to fix CVE-2026-32283

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-32283. EPSS is 0.62%. Act only if a listed version of If one side of is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-764; CWE-770: Allocation of Resources Without Limits or Throttling. EPSS 0.62%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 8, 2026 · NIST NVD

    Detected

    If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.

  2. Sep 18, 2026 · NIST NVD

    Updated

    If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.

Sources

  • CVE.orgVulnerability recordCVE-2026-32283

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-32283

    30-day exploitation probability 0.6%

    first.org
  • NIST NVDVulnerability recordCVE-2026-32283

    If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.