CVE-2026-116587
CVE
High
· CVSS 7.5
Medium Impactauth/validator: Go JOSE CPU Exhaustion via Oversized RSA Keys in Embedded JWKs
Exploitable under specific conditions
This vulnerability can affect KrakenD under specific conditions. Review the affected versions below and upgrade if your deployment is exposed.
Reachable on any endpoint protected by
auth/validator. KrakenD parses the token header
before it verifies the signature, so an unauthenticated client can send a token with a
crafted embedded JWK and repeat the request to keep the gateway CPU busy. Endpoints
without auth/validator are not exposed.Component
auth/validator
Disclosed
Nov 2, 2026
CVSS Score
7.5
Description
Go JOSE validates every RSA private key it parses from a JSON Web Key (JWK) by passing
the attacker-supplied
n, e, d, p and q values to crypto/rsa
PrivateKey.Validate(). Since Go 1.24 that validation is cubic in the size of the
modulus and primes, so a single JWK carrying huge primes burns an excessive amount of
CPU. The JWK does not need to come from a key set: a jwk parameter embedded in the
protected header of a JWS, which ParseSigned parses, is enough. Affects go-jose
v4 up to 4.1.5 and all v3 versions. Fixed in go-jose 4.1.6.Version summary
Community Edition
3.0.3
addresses this advisory
Affected CE versions
>= 2.0, < 3.0.3
Enterprise Edition
3.0.3, 2.13.13
addresses this advisory
Affected EE versions
>= 2.0, < 2.13.13 || >= 3.0, < 3.0.3
Upgrade to the addressed version or later to remediate this vulnerability.