CVE-2026-34986

Go JOSE affect by a panic in JWE decryption

HIGH
7.5
CVSS Score
Published: April 6, 2026 at 04:22 PM UTC
Updated: October 23, 2026 at 11:10 PM UTC
30 products affected across 3 vendorsGo JoseGo JoseEnterprise Linux

Using go-jose by go-jose?

Get instant alerts when new vulnerabilities affect go-jose - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

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.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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.0.0 ≤ v < 3.0.54.0.0 ≤ v < 4.1.4
Affected range stops below 3.0.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.4, so it looks safe — our inference, not a vendor statement
v < 3.0.5
Affected range stops below 3.0.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.4, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 1780204322 (unaffected)
Vendor states this is fixed in 2 (unaffected)
Vendor states this is fixed in 2 (unaffected)
Vendor states this is fixed in 0:0.144.0-2.el10_0 (unaffected)
Vendor states this is fixed in 0:0.144.0-2.el10_2 (unaffected)
Vendor states this is fixed in 0:0.144.0-2.el9_4 (unaffected)
Vendor states this is fixed in 0:0.144.0-2.el9_6 (unaffected)
Vendor states this is fixed in 0:0.144.0-2.el9_8 (unaffected)
Vendor states this is fixed in 0:1.1.2-1.el10_2 (unaffected)
Vendor states this is fixed in 0:101.3-4.el9_4.2 (unaffected)
Vendor states this is fixed in 0:101.5-1.el8_10 (unaffected)
Vendor states this is fixed in 0:132.2-8.el9_6 (unaffected)
Vendor states this is fixed in 0:134.1-9.el10_0 (unaffected)
Vendor states this is fixed in 0:165.1-2.el10_2 (unaffected)
Vendor states this is fixed in 0:165.1-2.el9_8 (unaffected)
Vendor states this is fixed in 0:52.1-1.el10_2 (unaffected)
Vendor states this is fixed in 0:52.1-1.el9_8 (unaffected)
Vendor states this is fixed in 10 (unaffected)
Vendor states this is fixed in 1:1.29.7-1.el9_2.5 (unaffected)
Vendor states this is fixed in 2:1.11.4-0.1.el9_2.6 (unaffected)
Vendor states this is fixed in 2:1.14.6-1.el9_4 (unaffected)
Vendor states this is fixed in 2:1.18.1-3.el10_0.1 (unaffected)
Vendor states this is fixed in 2:1.18.1-5.el9_6.1 (unaffected)
Vendor states this is fixed in 2:1.33.15-1.el9_4.1 (unaffected)
Vendor states this is fixed in 2:1.39.9-1.el10_0 (unaffected)
Vendor states this is fixed in 2:1.39.9-1.el9_6 (unaffected)
Vendor states this is fixed in 2:1.41.8-3.el9_7 (unaffected)
Vendor states this is fixed in 2:1.43.1-1.el9_8 (unaffected)
Vendor states this is fixed in 2:4.4.1-22.el9_2.11 (unaffected)
Vendor states this is fixed in 4:4.9.4-20.el9_4.3 (unaffected)
Vendor states this is fixed in 5:5.4.0-20.el9_6.3 (unaffected)
Vendor states this is fixed in 6:5.4.0-15.el10_0.1 (unaffected)
Vendor states this is fixed in 6:5.8.2-1.el9_8 (unaffected)
Vendor states this is fixed in 7:5.8.2-1.el10_2 (unaffected)
Vendor states this is fixed in 8080020260721142025.63b34585 (unaffected)
Vendor states this is fixed in 8100020260520103055.afee755d (unaffected)
Vendor states this is fixed in 8100020260701102925.afee755d (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (150)

x_refsource_CONFIRMMitigationVendor Advisory
Source: cverecord
https://github.com/go-jose/go-jose/security/advisories/GHSA-78h2-9frx-2jm8
x_refsource_MISCProductTechnical Description
Source: cverecord
https://pkg.go.dev/github.com/go-jose/go-jose/v4#pkg-constants
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:10125
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:10130
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:10135
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:10175
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:11070
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:11217

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-248CWE-131

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card