CVE-2026-34986

ADVISORY - github

Summary

Impact

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.

Fixed In

4.1.4 and v3.0.5

Workarounds

If the list of keyAlgorithms passed to ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() does not include key wrapping algorithms (those ending in KW), your application is unaffected.

If your application uses key wrapping, you can prevalidate to the JWE objects to ensure the encrypted_key field is nonempty. If your application accepts JWE Compact Serialization, apply that validation to the corresponding field of that serialization (the data between the first and second .).

Thanks

Thanks to Datadog's Security team for finding this issue.

EPSS Score⁠: 0.00651 (0.482)

Common Weakness Enumeration (CWE)

ADVISORY - nist

CWE-131⁠

Incorrect Calculation of Buffer Size

CWE-248⁠

Uncaught Exception

ADVISORY - github

CWE-248⁠

Uncaught Exception

ADVISORY - redhat

CWE-131⁠

Incorrect Calculation of Buffer Size

Impacted images

Advisories

GitHub

CREATED

5 months ago

UPDATED

4 months ago

ADVISORY IDGHSA-78h2-9frx-2jm8⁠

EXPLOITABILITY SCORE

3.9

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)

CWE-248⁠

CVSS SCORE

7.5high

Package	Type	OS Name	OS Version	Affected Ranges	Fix Versions
github.com/go-jose/go-jose/v4	golang	-	-	<4.1.4	4.1.4
github.com/go-jose/go-jose	golang	-	-	<=2.6.3	Not yet available
github.com/go-jose/go-jose/v3	golang	-	-	<3.0.5	3.0.5
github.com/go-jose/go-jose/v3	golang	-	-	<0.0.0-20260331235259-be2f6548701d	0.0.0-20260331235259-be2f6548701d
github.com/go-jose/go-jose/v4	golang	-	-	<0.0.0-20260331233350-0e59876635f3	0.0.0-20260331233350-0e59876635f3

CVSS:3 Severity and metrics

The CVSS metrics represent different qualitative aspects of a vulnerability that impact the overall score, as defined by the CVSS Specification⁠.

The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone). One example of an Adjacent attack would be an ARP (IPv4) or neighbor discovery (IPv6) flood leading to a denial of service on the local LAN segment (e.g., CVE-2013-6014).

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

The vulnerable system can be exploited without interaction from any user.

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

There is no loss of confidentiality.

There is no loss of trust or accuracy within the impacted component.

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component.

NIST

CREATED

4 months ago

UPDATED

CREATED

4 months ago

UPDATED

4 months ago

ADVISORY IDCVE-2026-34986⁠

EXPLOITABILITY SCORE

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)-

CVSS SCORE

N/Amedium

GoLang

CREATED

3 months ago

UPDATED

3 months ago

ADVISORY IDGO-2026-4945⁠

EXPLOITABILITY SCORE

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)-

EXPLOITS FOUND

COMMON WEAKNESS ENUMERATION (CWE)-

RATING UNAVAILABLE FROM ADVISORY

CVE-2026-34986

Summary

Impact

Fixed In

Workarounds

Thanks

Common Weakness Enumeration (CWE)

CWE-131⁠

CWE-248⁠

CWE-248⁠

CWE-131⁠

Advisories

GitHub

CVSS SCORE

Attack Vector (AV)Network

Attack Complexity (AC)Low

Privileges Required (PR)None

User Interaction (UI)None

Scope (S)Unchanged

Confidentiality (C)None

Integrity (I)None

Availability (A)High

NIST

CVSS SCORE

Alpine

Debian

Ubuntu

CVSS SCORE

GoLang

Alma

CVSS SCORE

Alma

CVSS SCORE

Alma

CVSS SCORE

Alma

CVSS SCORE

Alma

CVSS SCORE

Alma

CVSS SCORE

Alma

CVSS SCORE

Amazon

CVSS SCORE

Amazon

CVSS SCORE

Amazon

CVSS SCORE

Red Hat

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Rocky

CVSS SCORE

Oracle

CVSS SCORE

Oracle