CVE-2026-34986

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.4 and 3.0.5, decrypting a JSON Web Encryption (JWE) object will panic if the alg field indicates a key wrapping algorithm (one ending in KW, with the exception of A128GCMKW, A192GCMKW, and A256GCMKW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() in key_wrap.go attempts to allocate a slice with a zero or negative length based on the length of the encrypted_key. This code path is reachable from ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() followed by Decrypt() on the resulting object. Note that the parse functions take a list of accepted key algorithms. If the accepted key algorithms do not include any key wrapping algorithms, parsing will fail and the application will be unaffected. This panic is also reachable by calling cipher.KeyUnwrap() directly with any ciphertext parameter less than 16 bytes long, but calling this function directly is less common. Panics can lead to denial of service. This vulnerability is fixed in 4.1.4 and 3.0.5.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
46.9%
KEV
Not listed

Published

April 6, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated May 4, 2026
Patch available. Sources: github.
generic

jose package - github.com/go-jose/go-jose/v4 - Go Packages

https://pkg.go.dev/github.com/go-jose/go-jose/v4#pkg-constants
github Patch Available

Panic in JWE decryption · Advisory · go-jose/go-jose · GitHub

https://github.com/go-jose/go-jose/security/advisories/GHSA-78h2-9frx-2jm8

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/ose-kube-state-metrics-rhel9:17804026332026-06-11redhat
redhatrhoai/odh-model-controller-rhel9:17800693812026-06-10redhat
redhatrhacm2/submariner-rhel9-operator:17802043222026-06-10redhat
redhatquay/quay-rhel8:17808913952026-06-09redhat
redhatrhtas/rekor-monitor-rhel9:17800467532026-06-08redhat
redhatrhtas/updatetree-rhel9:17800535722026-06-08redhat
redhatrhtas/createtree-rhel9:17800535722026-06-08redhat
redhatrhtas/trillian-logsigner-rhel9:17800535722026-06-08redhat
redhatserve-tkn-cli-1-21-serve-tkn-cli-1.21.12026-06-08redhat
redhatrhtas/rhtas-console-rhel9:17803862992026-06-08redhat
redhatquay/quay-rhel8:17798114732026-06-04redhat
redhatimage-builder-0:52.1-1.el9_82026-06-04redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17801671182026-06-04redhat
redhatosbuild-composer-0:165.1-2.el9_82026-06-03redhat
redhatopenshift4/ose-operator-registry-rhel9:17797761412026-06-03redhat
redhatquay/quay-rhel8:17798222612026-06-03redhat
redhatimage-builder-0:52.1-1.el10_22026-06-03redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17792122592026-06-02redhat
redhatquay/quay-rhel8:17798114122026-06-02redhat
redhatquay/quay-rhel9:17799222052026-06-02redhat
redhatosbuild-composer-0:165.1-2.el10_22026-06-02redhat
redhatopenshift4/ose-cli-rhel9:17797759772026-06-02redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17795794392026-06-01redhat
redhatmulticluster-engine/assisted-service-8-rhel8:17799105042026-06-01redhat
redhatmulticluster-engine/assisted-service-9-rhel9:17799101292026-06-01redhat
redhatopenshift-pipelines/pipelines-operator-bundle:17800449552026-05-29redhat
redhatopenshift-pipelines/pipelines-pipelines-as-code-controller-rhel9:17798650012026-05-29redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17788677532026-05-28redhat
redhatopenshift4/ose-telemeter-rhel9:17792534522026-05-27redhat
redhatquay/quay-rhel8:17796893922026-05-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/go-jose/go-jose
github.com/go-jose/go-jose/v33.0.5
github.com/go-jose/go-jose/v44.1.4

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:05 UTCEPSS rescore
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-23 21:33 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 71 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 14:56 UTCEPSS rescore
  3. 2026-06-21 01:59 UTCEPSS rescore
  4. 2026-06-19 19:25 UTCEPSS rescore
  5. 2026-06-19 19:25 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-17 17:53 UTCEPSS rescore
  9. 2026-06-16 17:52 UTCEPSS rescore
  10. 2026-06-15 17:49 UTCEPSS rescore
  11. 2026-06-14 23:18 UTCEPSS rescore
  12. 2026-06-13 23:00 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-11 21:36 UTCEG score recompute
  16. 2026-06-11 21:36 UTCVendor advisory
  17. 2026-06-11 14:00 UTCEPSS rescore
  18. 2026-06-10 22:18 UTCEPSS rescore
  19. 2026-06-10 14:35 UTCEG score recompute
  20. 2026-06-10 14:35 UTCVendor advisory
  21. 2026-06-10 13:22 UTCEPSS rescore
  22. 2026-06-10 02:21 UTCEG score recompute
  23. 2026-06-10 02:21 UTCVendor advisory
  24. 2026-06-09 14:06 UTCEG score recompute
  25. 2026-06-09 14:06 UTCVendor advisory
  26. 2026-06-08 14:17 UTCEPSS rescore
  27. 2026-06-08 14:17 UTCEPSS rescore
  28. 2026-06-08 11:24 UTCEG score recompute
  29. 2026-06-08 11:24 UTCVendor advisory
  30. 2026-06-07 22:44 UTCEG score recompute
  31. 2026-06-07 22:44 UTCVendor advisory
  32. 2026-06-07 15:25 UTCEPSS rescore
  33. 2026-06-07 15:25 UTCEPSS rescore
  34. 2026-06-07 15:25 UTCEPSS rescore
  35. 2026-06-07 10:29 UTCEG score recompute
  36. 2026-06-07 10:29 UTCVendor advisory
  37. 2026-06-06 13:47 UTCEPSS rescore
  38. 2026-06-06 13:47 UTCEPSS rescore
  39. 2026-06-05 22:47 UTCEPSS rescore
  40. 2026-06-05 22:47 UTCEPSS rescore
  41. 2026-06-05 06:10 UTCEPSS rescore
  42. 2026-06-05 06:10 UTCEPSS rescore
  43. 2026-06-04 13:12 UTCEPSS rescore
  44. 2026-06-04 13:12 UTCEPSS rescore
  45. 2026-06-02 20:13 UTCEPSS rescore
  46. 2026-06-01 13:52 UTCEPSS rescore
  47. 2026-06-01 13:52 UTCEPSS rescore
  48. 2026-06-01 13:51 UTCEPSS rescore
  49. 2026-05-31 22:30 UTCEPSS rescore
  50. 2026-05-31 22:30 UTCEPSS rescore
  51. 2026-05-31 00:16 UTCEPSS rescore
  52. 2026-05-31 00:16 UTCEPSS rescore
  53. 2026-05-31 00:16 UTCEPSS rescore
  54. 2026-05-29 13:44 UTCEPSS rescore
  55. 2026-05-29 13:44 UTCEPSS rescore
  56. 2026-05-28 13:44 UTCEPSS rescore
  57. 2026-05-28 13:44 UTCEPSS rescore
  58. 2026-05-28 13:44 UTCEPSS rescore
  59. 2026-05-27 13:40 UTCEPSS rescore
  60. 2026-05-27 13:40 UTCEPSS rescore
  61. 2026-05-27 13:40 UTCEPSS rescore
  62. 2026-05-26 13:44 UTCEPSS rescore
  63. 2026-05-26 07:18 UTCEPSS rescore
  64. 2026-05-26 07:18 UTCEPSS rescore
  65. 2026-05-23 00:08 UTCEG score recompute
  66. 2026-05-20 22:38 UTCEPSS rescore
  67. 2026-05-20 22:38 UTCEPSS rescore
  68. 2026-05-20 18:54 UTCEG score recompute
  69. 2026-05-20 18:54 UTCVendor advisory
  70. 2026-05-20 11:22 UTCEPSS rescore
  71. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-34986?
CVE-2026-34986 is a high vulnerability published on April 6, 2026. 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.4 and 3.0.5, decrypting a JSON Web Encryption (JWE) object will…
When was CVE-2026-34986 disclosed?
CVE-2026-34986 was first published in the National Vulnerability Database on April 6, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34986 actively exploited?
CVE-2026-34986 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-34986?
CVE-2026-34986 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-34986?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34986, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-34986

Explore →

Is Your Infrastructure Affected by CVE-2026-34986?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.