Advisory record · GHSA-p45j-vfv5-wprq

RKE2 supervisor port is vulnerable to unauthenticated remote denial-of-service (DoS) attack via TLS SAN stuffing attack

CVSS 7.5 HighEPSS 0.0070 · 53rd percentile

Published by the GitHub Advisory Database at 11 Sept 2023, 13:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/rancher/rke2Go<1.24.17 || >=1.25.0, <1.25.13 || >=1.26.0, <1.26.8 || >=1.27.0, <1.27.5 || >=1.28.0, <1.28.11.24.17, 1.25.13, 1.26.8, 1.27.5, 1.28.1
Identifiers
GHSA-p45j-vfv5-wprq · CVE-2023-32186
Weakness (CWE)
CWE-770
Published
11 Sept 2023
Updated
4 May 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

RKE2 versions before 1.24.17, from 1.25.0 before 1.25.13, from 1.26.0 before 1.26.8, from 1.27.0 before 1.27.5, and from 1.28.0 before 1.28.1 are affected. An attacker with network access to the supervisor port (TCP 9345) can perform TLS handshakes without authentication and cause the certificate's SAN list to grow until TLS clients reject it, so servers and agents cannot establish new connections when joining or rejoining the cluster. Upgrade to 1.24.17, 1.25.13, 1.26.8, 1.27.5, 1.28.1 or later; on 1.27 or earlier, also set tls-san-security to true.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (suse)
  • CISA KEV Not listed.
  • EPSS 0.0070, the 53rd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.