7.5

CVE-2026-34986: Go JOSE affect by a panic in JWE decryption

Modified
AliasesRHSA-2026:10135RHSA-2026:19173RHSA-2026:19186
Published 06-04-2026Last modified 18-09-2026

Vulnerability summary

CVE-2026-34986 is a high (CVSS 7.5) Uncaught Exception vulnerability in go-jose_project go-jose. EPSS estimates a 0.66% chance of exploitation in the next 30 days, higher than 51.8% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 7.5 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 1% (FIRST, 04-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
0.66%
0%100%
Low · +0.01 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 97 · Related 59
OPENSUSE-SU-2026:10529-1OPENSUSE-SU-2026:10613-1OPENSUSE-SU-2026:10631-1OPENSUSE-SU-2026:10651-1OPENSUSE-SU-2026:10697-1OPENSUSE-SU-2026:10698-1

Timeline

  1. 06-04-2026
    PublishedVulnerability first disclosed.
  2. 18-09-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

9 scores · 9 sources · 1 version

EPSS trend

Probability

0.66%

Chance of exploitation in the next 30 days

Percentile

52%

Versus all other CVEs

30-day change

Increase +0.01 pp

From 0.65% on 05-10-2026

05-10-202604-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Chainguard199 products
  • aactl< 0.4.12-r50
  • agentbeat< 9.2.7-r1
  • agentbeat-fips< 9.2.7-r1
  • amazon-ssm-agent< 3.3.3270.0-r11
  • amazon-ssm-agent-ecs-exec< 3.3.3270.0-r11
Alpine1 product
  • skopeo< 1.20.1-r0

2 vendors · 200 products · Showing 200 of 1325

References

164 links
Show all 100 references

Showing 100 of 164.