CVE-2026-34986

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% 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, secondary
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 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)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

April 6, 2026

Last Modified

September 18, 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(29)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcri-o-0:1.25.5-36.rhaos4.12.git2e7f657.el82026-09-17redhat
redhatcri-o-0:1.26.5-32.rhaos4.13.git1088e36.el82026-09-17redhat
redhatcri-o-0:1.31.13-14.rhaos4.18.gitf2de9ac.el82026-09-17redhat
redhatopenshift4/ose-cloud-credential-rhel9-operator:17881620682026-09-10redhat
redhatcri-o-0:1.29.13-14.rhaos4.16.git84cfdc6.el82026-09-10redhat
redhatopenshift4/ose-cloud-credential-rhel9-operator:17875458312026-09-03redhat
redhatcri-o-0:1.32.13-11.rhaos4.19.git089e95c.el92026-09-02redhat
redhatdevspaces/udi-rhel9:17877648142026-09-01redhat
redhatcri-o-0:1.34.11-4.rhaos4.21.git358c4b4.el92026-09-01redhat
redhatcri-o-0:1.33.13-5.rhaos4.20.git7ebc848.el92026-09-01redhat
redhatopenshift4/ose-cloud-credential-rhel9-operator:17870088472026-08-26redhat
redhatopenshift4/ose-cloud-credential-rhel9-operator:17867697642026-08-26redhat
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17866443622026-08-19redhat
redhatopenshift4/ose-ovn-kubernetes-microshift-rhel9:17865729992026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatoadp/oadp-mustgather-rhel9:17851773592026-08-06redhat
redhatcontainer-tools:rhel8-8080020260721142025.63b345852026-08-04redhat
redhatopenshift4/ose-azure-workload-identity-webhook-rhel9:17852883552026-08-04redhat
redhatosbuild-composer-0:101.5-1.el8_102026-07-31redhat
redhatopenshift-logging/lokistack-gateway-rhel9:17847478162026-07-29redhat
redhatquay/quay-rhel9:17849872732026-07-29redhat
redhatopenshift4/ose-azure-workload-identity-webhook-rhel9:17843435782026-07-28redhat
redhatmulticluster-engine/must-gather-rhel9:17848498672026-07-28redhat
redhatrhmtc/openshift-migration-controller-rhel8:17839533722026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836853752026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836775332026-07-20redhat

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

(15 across 5 ecosystems)
Debian:13(4)
PackageVulnerable rangeFixed inDependents
golang-github-go-jose-go-jose4.0.5-1, 4.1.3-1, 4.1.4-1, 4.1.4-1~bpo13+1, 4.1.4-2
golang-github-go-jose-go-jose.v33.0.3-6
golang-gopkg-square-go-jose.v11.1.2-4
golang-gopkg-square-go-jose.v22.6.3-3, 2.6.3-4, 2.6.3-4~exp0
Debian:14(4)
PackageVulnerable rangeFixed inDependents
golang-github-go-jose-go-jose4.0.5-1, 4.1.3-1, 4.1.4-1~bpo13+14.1.4-1
golang-github-go-jose-go-jose.v33.0.3-6
golang-gopkg-square-go-jose.v11.1.2-4
golang-gopkg-square-go-jose.v22.6.3-3, 2.6.3-4, 2.6.3-4~exp0
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
Debian:11(2)
PackageVulnerable rangeFixed inDependents
golang-gopkg-square-go-jose.v11.1.2-2, 1.1.2-3, 1.1.2-3.1, 1.1.2-4
golang-gopkg-square-go-jose.v22.5.1-2 ... 2.6.3-4~exp0 (8 versions)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
golang-gopkg-square-go-jose.v11.1.2-4
golang-gopkg-square-go-jose.v22.6.0-2 ... 2.6.3-4~exp0 (6 versions)

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 22× in last 7d / 95× 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.

Showing the most recent 100 of 320 total refreshes for this CVE.

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

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 September 18, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 50.3% of all scored CVEs.
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.