# CVE-2026-116586: Go JOSE: Panics in JSON parsing

CVE-2026-116586 is fixed in google-cloud-sap-agent on 1 platform by SUSE-SU-2026:24604-1 (version 3.15-160000.5.1), released November 8, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-116586
- Priority: Routine
- CVSS: n/a (Moderate)
- EPSS: 0.0029
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Oct 31, 2026
- Weakness: Uncontrolled Recursion
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-116586

## Description

This update for google-cloud-sap-agent fixes the following issues:  - CVE-2026-78659: golang.org/x/net/http2: HTTP/2 server memory exhaustion due to Trailer headers (bsc#1286994). - CVE-2026-78660: golang.org/x/net/http2: HTTP/2 transport accepts malformed framing-related headers (bsc#1287058). - CVE-2026-78663: golang.org/x/net/http2: double flow control refund on HTTP/2 server streams (bsc#1287137). - CVE-2026-78669: golang.org/x/net/http2: excessive CPU consumption from repeated initial window changes (bsc#1285292). - CVE-2026-97032: golang.org/x/net/http2: HTTP/2 server crash due to HPACK encoder race (bsc#1287487). - CVE-2026-116585,CVE-2026-116586,CVE-2026-116587: github.com/go-jose/go-jose/v4: multiple security issues in   github.com/go-jose/go-jose before 4.1.6 (bsc#1288375).

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | google-cloud-sap-agent sles 16.0 | 3.15-160000.5.1 | [SUSE-SU-2026:24604-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24604-1.md) | Nov 8, 2026 |

---

Data as of 2026-11-10T13:56:55Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.