Allocation of Resources Without Limits or Throttling Affecting github.com/rancher/rancher/pkg/auth/audit package, versions >=2.12.0-alpha1 <2.12.12-alpha8>=2.13.0-alpha1 <2.13.8-alpha8>=2.14.0-alpha1 <2.14.4-alpha6
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMRANCHERRANCHERPKGAUTHAUDIT-18600448
- published9 Aug 2026
- disclosed5 Aug 2026
- creditBenTheCyberOne
Introduced: 5 Aug 2026
CVE-2026-59675 Â (opens in a new tab)How to fix?
Upgrade github.com/rancher/rancher/pkg/auth/audit to version 2.12.12-alpha8, 2.13.8-alpha8, 2.14.4-alpha6 or higher.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the copyReqBody function in pkg/auth/audit/log.go. An attacker can exhaust server memory and crash the Rancher Manager process by sending arbitrarily large HTTP request bodies to the public login endpoints when API audit logging is enabled. The audit middleware reads the full login request body into memory before Rancher's normal body-size limit is applied, so a few concurrent oversized login requests can consume enough RAM to make the Rancher API and UI unavailable and disrupt management of downstream clusters.
Notes
- API audit logging must be enabled for the vulnerable path to run; deployments with audit logging off are not affected by this middleware issue.
- The affected login handlers are the public
v3-public/localProviders/local?action=loginrequests, and the normalAPIBodyLimitingHandlercap is bypassed on that audit-log path, so the default 1 MiB request-body limit does not protect those requests.