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 52% 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
48%
KEV
Not listed

Published

April 6, 2026

Last Modified

August 25, 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

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 / EcosystemFixed in / PatchReleasedSource
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatodf4/rook-ceph-rhel9-operator:17866443622026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatopenshift4/ose-ovn-kubernetes-microshift-rhel9:17865729992026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatoadp/oadp-mustgather-rhel9:17851773592026-08-06redhat
redhatopenshift4/ose-azure-workload-identity-webhook-rhel9:17852883552026-08-04redhat
redhatcontainer-tools:rhel8-8080020260721142025.63b345852026-08-04redhat
redhatosbuild-composer-0:101.5-1.el8_102026-07-31redhat
redhatquay/quay-rhel9:17849872732026-07-29redhat
redhatopenshift-logging/lokistack-gateway-rhel9:17847478162026-07-29redhat
redhatmulticluster-engine/must-gather-rhel9:17848498672026-07-28redhat
redhatopenshift4/ose-azure-workload-identity-webhook-rhel9:17843435782026-07-28redhat
redhatodf4/rook-ceph-rhel9-operator:17836775332026-07-20redhat
redhatrhmtc/openshift-migration-controller-rhel8:17839533722026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836853752026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836692192026-07-16redhat
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat
redhatopenshift4/ose-oauth-server-rhel9:17821855512026-07-09redhat
redhatdevspaces/udi-base-rhel10:17829874302026-07-08redhat
redhatopenshift4/ose-agent-installer-node-agent-rhel9:17828799902026-07-07redhat
redhatcontainer-tools:rhel8-8100020260701102925.afee755d2026-07-06redhat
redhatopenshift-logging/lokistack-gateway-rhel9:17823929612026-07-01redhat
redhatskopeo-2:1.14.6-1.el9_42026-07-01redhat
redhatpodman-4:4.9.4-20.el9_4.32026-07-01redhat
redhatbuildah-2:1.33.15-1.el9_4.12026-07-01redhat
redhatcontainer-tools:rhel8-8100020260520103055.afee755d2026-06-30redhat
redhatosbuild-composer-0:101.3-4.el9_4.22026-06-29redhat

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/v3—3.0.5—
github.com/go-jose/go-jose/v4—4.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 25× in last 7d / 131× 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 245 total refreshes for this CVE.

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

Start Free Scan →Browse All CVEs