Skip to content
Fencer Vulns
high 7.5

CVE-2026-116587 json

Go JOSE: DoS when parsing JWKs that contain RSA keys

published 2026-10-26 13 d ago modified 2026-10-27 12 d ago also GHSA-mgcc-cww5-fp2q , EUVD-2026-110467

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/go-jose/go-jose/v4 4.1.6
  • google-cloud-sap-agent SLES for SAP applications 16.0, SLES 16.0 3.15-160000.5.1

suse advisories SUSE-SU-2026:24604-1

  • skopeo openSUSE Tumbleweed 1.24.0-2.1

opensuse advisories openSUSE-SU-2026:12478-1

  • docker Alpine 3.24 29.9.3-r0

alpine advisories ALPINE-CVE-2026-116587

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-116587 updated cvss 7.5

github.com/go-jose/go-jose: go-jose: Denial of Service via crafted RSA parameters in JWKs

  • Red Hat Multicluster Engine for Kubernetes multicluster-engine/kube-rbac-proxy-mce-rhel9
    affected: workaround, no fix available
  • Red Hat OpenShift Service Mesh 3 openshift-service-mesh/kiali-rhel9-operator
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/kube-rbac-proxy-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-mod-arch-gen-ai-rhel9, rhoai/odh-model-controller-rhel9, rhoai/odh-kserve-controller-rhel9, rhoai/odh-kserve-llmisvc-controller-rhel9, rhoai/odh-trustyai-service-operator-rhel9 Red Hat OpenShift Container Platform 4 openshift4/ose-kube-rbac-proxy-rhel9, openshift4/ose-agent-installer-api-server-rhel8, openshift4/ose-agent-installer-api-server-rhel9, openshift4/ose-agent-installer-orchestrator-rhel8, openshift4/ose-agent-installer-orchestrator-rhel9, openshift4/ose-openshift-controller-manager-rhel8
    affected: workaround, no fix available
  • Red Hat OpenShift Service Mesh 3 openshift-service-mesh/kiali-rhel9, openshift-service-mesh/kiali-operator-bundle
    not affected: component not present
  • Red Hat OpenShift Container Platform 4 openshift4/ose-agent-installer-node-agent-rhel9, openshift4/ose-agent-installer-csr-approver-rhel8, openshift4/ose-agent-installer-csr-approver-rhel9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
12 d ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/go-jose/go-jose/v4
<4.1.6
4.1.6
go github.com/go-jose/go-jose/v3
<=3.0.5
 no fix listed

Affected products

  • go-jose go-jose

Classification

Weakness
  • CWE-407 Inefficient Algorithmic Complexity
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.