# CVE-2026-116586: Go JOSE: Panics in JSON parsing - **Severity:** Medium 6.9 (`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`) - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 26 Oct 2026 - **Updated:** 26 Oct 2026 - **Also known as:** GHSA-vvm8-gf78-28g4, MINI-2px7-29cf-7q95, MINI-36qq-pcp3-67rf, MINI-3g94-5wxw-w946, MINI-3hr3-g42v-5g95, MINI-47x5-q4qm-m296, MINI-494v-xm8j-fjmh, MINI-4g87-69cf-9cg2, MINI-5wvf-7cwf-hr6c, MINI-63mw-7x62-74g8, MINI-678g-j8r5-4v76, MINI-6c5j-g68q-wv84, MINI-79qx-fv5p-jvpf, MINI-7g96-7f44-vhpx, MINI-834g-262f-p463, MINI-84vc-ph8c-827r, MINI-86cj-j743-q6r2, MINI-89hx-mjhq-mc27, MINI-8c44-9c8v-8499, MINI-8cmq-3gqf-xp4q, MINI-8gmx-xwp5-v8rf, MINI-8jh9-x7j7-chvv, MINI-8w75-2hfr-frh3, MINI-98xp-rq4j-r23f, MINI-9g9g-qcvp-6q4c, MINI-9w2w-5pf7-whg5, MINI-c6mr-r3q5-hj86, MINI-ch39-6x34-prph, MINI-cvc5-v5cr-48m2, MINI-f5h9-q6h6-9x4q, MINI-f7hq-f83h-qm8r, MINI-g83h-j978-cvhm, MINI-g97v-h5m4-v3c2, MINI-grf7-ghpp-4q37, MINI-h98w-5w38-vg9r, MINI-hq38-865p-f4v5, MINI-m23c-p5q3-pf7q, MINI-prh4-5r76-pjq8, MINI-q6r6-2vpj-j8gc, MINI-q8gh-gxgp-8c7h, MINI-qfqf-4mjf-6mx5, MINI-r283-rhh7-v936, MINI-r3xh-4mwj-vwfm, MINI-r4h2-h2c3-xpjv, MINI-r5qx-rv5w-9vwx, MINI-rvr5-7ffp-chj7, MINI-vcgq-rf6c-q8vp, MINI-vf9w-g828-x2cr, MINI-vg9w-3g93-p472, MINI-vwm3-p44c-r29j, MINI-w55x-5q67-92m7, MINI-w7j2-vrw5-fh64, MINI-wv7j-gvgm-r8r8, MINI-x3g3-c3j8-6vqc, MINI-xgr6-prfh-q682, MINI-xvp4-h278-fc79, UBUNTU-CVE-2026-116586 ## What is CVE-2026-116586? CVE-2026-116586 is a medium-severity vulnerability in go-jose, published on 26 Oct 2026. ### Official 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. Weakness: CWE-674 (Uncontrolled Recursion) ## Which versions are affected by CVE-2026-116586? 4 open source packages ship an affected version, including github.com/go-jose/go-jose/v3 and github.com/go-jose/go-jose/v4. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/go-jose/go-jose/v3` | Go | All versions to 3.0.5 | None | | `github.com/go-jose/go-jose/v3` | Go | All versions to 3.0.5 | None | | `github.com/go-jose/go-jose/v4` | Go | All versions | 4.1.5 | | `github.com/go-jose/go-jose/v4` | Go | All versions | 4.1.5 | ## How do I fix CVE-2026-116586? Upgrade to a fixed version. ## Is CVE-2026-116586 being exploited? There is no known exploitation of CVE-2026-116586 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-116586 and fix it if it is affected. What it is: CVE-2026-116586 is a medium-severity vulnerability in go-jose, published on 26 Oct 2026. Exploitation: There is no known exploitation of CVE-2026-116586 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/go-jose/go-jose/v3 (Go): affected all versions up to 3.0.5; no fix listed - github.com/go-jose/go-jose/v3 (Go): affected all versions up to 3.0.5; no fix listed - github.com/go-jose/go-jose/v4 (Go): affected all versions; fixed in 4.1.5 - github.com/go-jose/go-jose/v4 (Go): affected all versions; fixed in 4.1.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-116586/ (Markdown: https://insights.sbomify.com/CVE-2026-116586/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116586 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116586 - OSV: https://osv.dev/vulnerability/CVE-2026-116586 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-116586/ Summaries are generated and may contain mistakes; the official description above is the record.