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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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%
EPSS PROB
0.7%
EPSS %ILE
49th
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
githubMentions a patch (unverified)

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

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

Vendor Advisories for CVE-2026-34986(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(29)

Vendor / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
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
  • every version on: no fix on record
—
golang-github-go-jose-go-jose.v33.0.3-6
  • every version on: no fix on record
—
golang-gopkg-square-go-jose.v11.1.2-4
  • every version on: no fix on record
—
golang-gopkg-square-go-jose.v22.6.3-3, 2.6.3-4, 2.6.3-4~exp0
  • every version on: no fix on record
—
Debian:14(4)
PackageVulnerable rangeFix by version rangeDependents
golang-github-go-jose-go-jose4.0.5-1, 4.1.3-1, 4.1.4-1~bpo13+1
  • every version up to 4.1.4-1: fixed in 4.1.4-1
—
golang-github-go-jose-go-jose.v33.0.3-6
  • every version on: no fix on record
—
golang-gopkg-square-go-jose.v11.1.2-4
  • every version on: no fix on record
—
golang-gopkg-square-go-jose.v22.6.3-3, 2.6.3-4, 2.6.3-4~exp0
  • every version on: no fix on record
—
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/go-jose/go-jose—
  • every version through 2.6.3: no fix on record
—
github.com/go-jose/go-jose/v3—
  • every version up to 3.0.5: fixed in 3.0.5
—
github.com/go-jose/go-jose/v4—
  • every version up to 4.1.4: fixed in 4.1.4
—
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
golang-gopkg-square-go-jose.v11.1.2-2, 1.1.2-3, 1.1.2-3.1, 1.1.2-4
  • every version on: no fix on record
—
golang-gopkg-square-go-jose.v22.5.1-2 ... 2.6.3-4~exp0 (8 versions)
  • every version on: no fix on record
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
golang-gopkg-square-go-jose.v11.1.2-4
  • every version on: no fix on record
—
golang-gopkg-square-go-jose.v22.6.0-2 ... 2.6.3-4~exp0 (6 versions)
  • every version on: no fix on record
—

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 / 46× 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 335 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Same product

5 shown

Debian:11:golang-gopkg-square-go-jose.v2 · Go:github.com/go-jose/go-jose · Debian:11:golang-gopkg-square-go-jose.v1

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 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 0.7% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-34986?
CVE-2026-34986 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-34986?
A fix for CVE-2026-34986 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-34986 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs