Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
Keda may run out of memory and stop service
published 1 year ago
Summary
Keda uses the Go JOSE library, and versions before 4.0.5 can consume a lot of memory when processing specially crafted tokens that contain many periods. This can cause the application to run out of memory and become unavailable. Upgrade the library to version 4.0.5 or later, or add a check to reject tokens with an excessive number of periods before they are processed.
What to do
- Update azure keda to version 2.14.1-3.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Azure Linux:3 | azure | keda |
< 2.14.1-3 Fix: upgrade to 2.14.1-3
|
Original advisory text
CVE-2025-27144 affecting package keda for versions less than 2.14.1-3
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of `.` characters.
References
Timeline
Published24 Feb 2025
Updated23 Sep 2026
First seen23 Sep 2026
Sources
AZL-57165 · OSV
Track software like this
Free during beta