Live › vulnerability › CVE-2026-116587
Go to dashboardgo-jose parses RSA modulus and prime values from JWKs without size checks, so a crafted key makes Go's RSA validation take cubic CPU time. An attacker who can submit JWKs to an application that parses untrusted keys can cause a remote denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 22:25 UTC. All times on this page are UTC.
Applications that import go-jose and parse JSON Web Keys supplied by untrusted parties, such as public JWKS endpoints or user-submitted keys, on Go 1.24 or later. Services that only handle keys they load from their own configuration, or that never parse attacker-supplied JWKs, are not exposed.
No product ranges from the sources yet.
go.mod (for example grep go-jose go.mod); versions below 4.1.6 are affected.1.24 or later with go version, since the slowdown depends on that release.4.1.6 or later (go get github.com/go-jose/go-jose/[email protected]).Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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. Prior to 4.1.6, go-jose parses attacker-controlled RSA modulus and prime values from JWKs without enforcing size and consistency bounds before passing them to crypto/rsa.PrivateKey.Validate. On Go 1.24 and later, crafted large or degenerate RSA parameters can make that validation consume cubic CPU time, allowing remote denial of service in applications that parse JWKs from untrusted sources. This issue is fixed in version 4.1.6.
This page as .md · .json · in your agent: get_signal("CVE-2026-116587")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.