CVE-2026-116586: go-jose · Uncontrolled Recursion
Affects go-joseSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.1.5 when convenient.
Data as of 26 Oct 2026, 21:42 UTC
- Patch
- Available – fixed in 4.1.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade go-jose to 4.1.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| go-josego-jose | Affected
| Fixed in
|
Description
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.5, parsing attacker-controlled JSON through go-jose allows deeply nested arrays or objects to exceed Go's stack limit. The resulting stack overflow crashes the application and permits denial of service in applications that parse untrusted JSON through go-jose. This issue is fixed in version 4.1.5.
References
- github.com/go-jose/go-jose/security/advisories/GHSA-vvm8-gf78-28g4 (opens in a new tab)
- github.com/go-jose/go-jose/pull/290 (opens in a new tab)
- github.com/go-jose/go-jose/commit/a31af25836222f4c45d366d6e8f9b1049dd9935a (opens in a new tab)
- github.com/go-jose/go-jose/releases/tag/v4.1.5 (opens in a new tab)