Skip to content
Fencer Vulns
high 7.5

CVE-2023-32186 json

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

published 2023-09-11 3 y ago modified 2026-06-17 4 mo ago also GHSA-p45j-vfv5-wprq , EUVD-2023-2553

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

A Allocation of Resources Without Limits or Throttling vulnerability in SUSE RKE2 allows attackers with access to K3s servers apiserver/supervisor port (TCP 6443) cause denial of service. This issue affects RKE2: from 1.24.0 before 1.24.17+rke2r1, from v1.25.0 before v1.25.13+rke2r1, from v1.26.0 before v1.26.8+rke2r1, from v1.27.0 before v1.27.5+rke2r1, from v1.28.0 before v1.28.1+rke2r1.

Patch / fix

  • go github.com/rancher/rke2 1.24.17, 1.25.13, 1.26.8, 1.27.5, 1.28.1
  • SUSE RKE2 .27.5\+/rke2r1, 1.24.17\+/rke2r1, 1.24.17+rke2r1, 1.25.13\+/rke2r1, 1.26.8\+/rke2r1, 1.28.1\+/rke2r1, v1.25.13+rke2r1, v1.26.8+rke2r1, v1.27.5+rke2r1, v1.28.1+rke2r1

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/rancher/rke2
<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.1
1.24.17
1.25.13
1.26.8
1.27.5
1.28.1

Affected products

  • SUSE RKE2

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.