cve.bz

CVE-2026-116586 go-jose go-jose: Uncontrolled Recursion

6.9 mediumEPSS 0.3%Fix available

Medium (6.9) in go-jose go-jose. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/go-jose/go-jose/v4 4.1.5.

On this page
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.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-674 Uncontrolled Recursion
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-116586 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116586?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116586?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116586 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
go-jose< 4.1.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vvm8-gf78-28g4Gogithub.com/go-jose/go-jose/v4<4.1.54.1.5
GHSA-vvm8-gf78-28g4Gogithub.com/go-jose/go-jose/v3<=3.0.5no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12golang-gopkg-square-go-jose.v1, golang-gopkg-square-go-jose.v2no fix listedDEBIAN-CVE-2026-116586
Debian13, 14golang-github-go-jose-go-jose, golang-gopkg-square-go-jose.v1, golang-gopkg-square-go-jose.v2 and 1 moreno fix listedDEBIAN-CVE-2026-116586
Ubuntu20.04:LTS, 22.04:LTSgolang-gopkg-square-go-jose.v2no fix listedUBUNTU-CVE-2026-116586
Ubuntu24.04:LTSgolang-github-go-jose-go-jose, golang-gopkg-square-go-jose.v2no fix listedUBUNTU-CVE-2026-116586
Ubuntu26.04:LTSgolang-gopkg-square-go-jose.v2, golang-github-go-jose-go-jose.v3no fix listedUBUNTU-CVE-2026-116586
Ubuntu26.10golang-github-go-jose-go-jose, golang-gopkg-square-go-jose.v2, golang-github-go-jose-go-jose.v3no fix listedUBUNTU-CVE-2026-116586
UbuntuPro:26.04:LTSgolang-github-go-jose-go-joseno fix listedUBUNTU-CVE-2026-116586
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 9 moreskopeo1.14.4-150300.11.25.1SUSE-SU-2026:5193-1
SUSELinux Enterprise Micro 5.5, Linux Enterprise Module for Public Cloud 15 SP4, Linux Enterprise Module for Public Cloud 15 SP5 and 2 moregoogle-osconfig-agent20261105.03-150000.1.83.1SUSE-SU-2026:5246-1
SUSELinux Enterprise Module for Public Cloud 12google-cloud-sap-agent3.16-6.90.1SUSE-SU-2026:5242-1
SUSELinux Enterprise Module for Public Cloud 12google-osconfig-agent20261105.03-1.76.1SUSE-SU-2026:5245-1
SUSELinux Enterprise Module for Public Cloud 15 SP4, Linux Enterprise Module for Public Cloud 15 SP5, Linux Enterprise Module for Public Cloud 15 SP6 and 1 moreazure-storage-azcopy10.34.1-150400.9.28.1SUSE-SU-2026:5241-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0google-cloud-sap-agent3.15-160000.5.1SUSE-SU-2026:24604-1
SUSELinux Enterprise Server 16.1, Linux Enterprise Server for SAP applications 16.1google-cloud-sap-agent3.15-160100.4.1SUSE-SU-2026:24616-1
SUSELinux Enterprise Server for NVIDIA 16.1google-cloud-sap-agent3.15-160100.4.1SUSE-SU-2026:24699-1
openSUSELeap 16.0google-cloud-sap-agent3.15-160000.5.1openSUSE-SU-2026:22236-1
openSUSELeap 16.0trivy0.76.2-160000.1.1openSUSE-SU-2026:22273-1
openSUSELeap 16.1google-cloud-sap-agent3.15-160100.4.1openSUSE-SU-2026:22297-1
openSUSETumbleweedskopeo1.24.0-2.1openSUSE-SU-2026:12478-1
Azure Linux3azcopyno fix listedAZL-111808
Azure Linux3buildahno fix listedAZL-111682
Azure Linux3cert-managerno fix listedAZL-111821
Azure Linux3containerd2no fix listedAZL-111869
Azure Linux3containerized-data-importerno fix listedAZL-111875
Azure Linux3cri-ono fix listedAZL-111685
Azure Linux3dcos-clino fix listedAZL-111905
Azure Linux3docker-buildxno fix listedAZL-111923
Azure Linux3docker-clino fix listedAZL-111929
Azure Linux3docker-composeno fix listedAZL-111932
Azure Linux3ignition-flatcarno fix listedAZL-111962
Azure Linux3influxdbno fix listedAZL-111971
9 more for Azure Linux in the JSON.

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having Important impact because an unauthenticated remote attacker can trigger a denial of service against services that process JOSE structures, causing affected components to crash without recovery. In Red Hat environments such as OpenShift and Advanced Cluster Management, go-jose is integrated into core control plane proxies and management services that inspect incoming tokens. While the issue does not lead to confidentiality or integrity loss or code execution, terminating these daemons interrupts critical cluster authentication and administrative operations.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

--- CME Mitigation Guidance (2026-11-02) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to enforce nesting depth limits and input size bounds on incoming JSON payloads before parsing them with go-jose: upgrade to go-jose 4.1.5 (or the corresponding fixed Red Hat builds), which enforce a maximum JSON nesting depth limit of 10,000 in pushParseState and return an error when exceeded, closing all 2 injection vectors (deeply nested JSON arrays, deeply nested JSON objects). Until patched, this is a concern on Applications and services parsing untrusted JSON or JOSE tokens with go-jose, so Reject large inputs before parsing and restrict unauthenticated network access to endpoints handling untrusted JOSE tokens. As a compensating measure, Configure systemd service watchdogs and automatic restart settings to recover daemons following fatal stack overflow crashes. These controls limit blast radius and contain exploitation, but they do not fix the underlying unbounded recursion stack overflow defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1311 Input Size and Quantity Bounds Enforcement (high)

ProductPackageStateAdvisory
Multicluster Engine for Kubernetesmulticluster-engine/kube-rbac-proxy-mce-rhel9Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-cache-rhel9Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-chains-controller-rhel9Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-cli-tkn-rhel9Not affected
OpenShift Pipelinesopenshift-pipelines/pipelines-controller-rhel9Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-opc-rhel9Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-pipelines-as-code-controller-rhel9Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-results-api-rhel9Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-results-watcher-rhel9Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-rhel9-operatorAffected
OpenShift Pipelinesopenshift-pipelines/pipelines-sidecarlogresults-rhel9Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-triggers-eventlistenersink-rhel9Affected
OpenShift Service Mesh 3openshift-service-mesh/kiali-operator-bundleNot affected
OpenShift Service Mesh 3openshift-service-mesh/kiali-rhel9Not affected
OpenShift Service Mesh 3openshift-service-mesh/kiali-rhel9-operatorWill not fix
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/kube-rbac-proxy-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-controller-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-llmisvc-controller-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-mod-arch-gen-ai-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-model-controller-rhel9Affected
10 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116586.

Attack patterns (CAPEC)

  • CAPEC-230 Serialized Data with Nested Payloads Likelihood: Medium · Severity: High
  • CAPEC-231 Oversized Serialized Data Payloads Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON