CVE-2026-34986: Go JOSE affect by a panic in JWE decryption
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.66% (FIRST EPSS); higher than 51.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: go-jose go-jose 4.1.4.
Low priority for now. Upgrade to go-jose go-jose 4.1.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- GHSA-78h2-9frx-2jm8
- ALSA-2026:10135
- ALSA-2026:19017
- ALSA-2026:19135
- ALSA-2026:19173
- ALSA-2026:19186
- ALSA-2026:19353
- ALSA-2026:33722
- ALSA-2026:35833
- ALSA-2026:48790
- GO-2026-4945
- openSUSE-SU-2026:10529-1
- openSUSE-SU-2026:10577-1
- openSUSE-SU-2026:10613-1
- openSUSE-SU-2026:10630-1
- openSUSE-SU-2026:10631-1
- openSUSE-SU-2026:10651-1
- openSUSE-SU-2026:10654-1
- openSUSE-SU-2026:10655-1
- openSUSE-SU-2026:10677-1
- Published
- Apr 6, 2026
- Updated
- Oct 23, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- CWE-248
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| go-jose project | go-jose | cpe:2.3:a:go-jose_project:go-jose |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- go-jose project go-jose3.0.0 and later · before 3.0.5
- go-jose project go-jose4.0.0 and later · before 4.1.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
go-jose go-jose
- >= 4.0.0, < 4.1.4, < 3.0.5affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | opentelemetry-collector | before 0.144.0-2.el10_2 | 0.144.0-2.el10_2 |
| AlmaLinux:10 | podman | before 7:5.8.2-1.el10_2.alma.1 | 7:5.8.2-1.el10_2.alma.1 |
| AlmaLinux:10 | podman-docker | before 7:5.8.2-1.el10_2.alma.1 | 7:5.8.2-1.el10_2.alma.1 |
| AlmaLinux:10 | podman-remote | before 7:5.8.2-1.el10_2.alma.1 | 7:5.8.2-1.el10_2.alma.1 |
| AlmaLinux:10 | podman-tests | before 7:5.8.2-1.el10_2.alma.1 | 7:5.8.2-1.el10_2.alma.1 |
| AlmaLinux:8 | aardvark-dns | before 2:1.10.1-2.module_el8.10.0+3901+4b80ecd7 | 2:1.10.1-2.module_el8.10.0+3901+4b80ecd7 |
| AlmaLinux:8 | aardvark-dns | before 2:1.10.1-2.module_el8.10.0+4047+545787c4 | 2:1.10.1-2.module_el8.10.0+4047+545787c4 |
| AlmaLinux:8 | aardvark-dns | before 2:1.10.1-2.module_el8.10.0+4089+ce72bbbe | 2:1.10.1-2.module_el8.10.0+4089+ce72bbbe |
| AlmaLinux:8 | aardvark-dns | before 2:1.10.1-2.module_el8.10.0+3909+6e1c1eb7 | 2:1.10.1-2.module_el8.10.0+3909+6e1c1eb7 |
| AlmaLinux:8 | buildah | before 2:1.33.14-4.module_el8.10.0+4213+0493256b | 2:1.33.14-4.module_el8.10.0+4213+0493256b |
| AlmaLinux:8 | buildah | before 2:1.33.14-3.module_el8.10.0+4211+49ea0979 | 2:1.33.14-3.module_el8.10.0+4211+49ea0979 |
| AlmaLinux:8 | buildah-tests | before 2:1.33.14-3.module_el8.10.0+4211+49ea0979 | 2:1.33.14-3.module_el8.10.0+4211+49ea0979 |
| AlmaLinux:8 | buildah-tests | before 2:1.33.14-4.module_el8.10.0+4213+0493256b | 2:1.33.14-4.module_el8.10.0+4213+0493256b |
| AlmaLinux:8 | buildah-tests | before 2:1.33.14-3.module_el8.10.0+4136+16425343 | 2:1.33.14-3.module_el8.10.0+4136+16425343 |
| AlmaLinux:8 | cockpit-podman | before 84.1-1.module_el8.10.0+4102+6c76e544 | 84.1-1.module_el8.10.0+4102+6c76e544 |
| AlmaLinux:8 | conmon | before 3:2.1.10-1.module_el8.10.0+4068+0e21408f | 3:2.1.10-1.module_el8.10.0+4068+0e21408f |
| AlmaLinux:8 | conmon | before 3:2.1.10-1.module_el8.10.0+4090+91932338 | 3:2.1.10-1.module_el8.10.0+4090+91932338 |
| AlmaLinux:8 | conmon | before 3:2.1.10-1.module_el8.10.0+3970+8445edf6 | 3:2.1.10-1.module_el8.10.0+3970+8445edf6 |
| AlmaLinux:8 | container-selinux | before 2:2.229.0-3.module_el8.10.0+4211+49ea0979 | 2:2.229.0-3.module_el8.10.0+4211+49ea0979 |
| AlmaLinux:8 | container-selinux | before 2:2.229.0-3.module_el8.10.0+4213+0493256b | 2:2.229.0-3.module_el8.10.0+4213+0493256b |
| AlmaLinux:8 | containernetworking-plugins | before 1:1.4.0-8.module_el8.10.0+4136+16425343 | 1:1.4.0-8.module_el8.10.0+4136+16425343 |
| AlmaLinux:8 | containers-common | before 2:1-82.module_el8.10.0+4089+ce72bbbe | 2:1-82.module_el8.10.0+4089+ce72bbbe |
| AlmaLinux:8 | containers-common | before 2:1-82.module_el8.10.0+3901+4b80ecd7 | 2:1-82.module_el8.10.0+3901+4b80ecd7 |
| AlmaLinux:8 | containers-common | before 2:1-82.module_el8.10.0+3876+e55593a8 | 2:1-82.module_el8.10.0+3876+e55593a8 |
+96
Same product
go-jose project: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-9121go-jose before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm.36Monitor
- CVE-2016-9123go-jose before 1.0.5 suffers from a CBC-HMAC integer overflow on 32-bit architectures.31Monitor
- CVE-2016-9122go-jose before 1.0.4 suffers from multiple signatures exploitation.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-28180Mar 8, 2024 · Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification)18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| go-jose go-jose | 4.1.4 · description | Vendor (CNA) |
| almalinux:aardvark-dns | 2:1.10.1-2.module_el8.10.0+3909+6e1c1eb7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:buildah | 2:1.41.8-3.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:buildah-tests | 2:1.41.8-3.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:cockpit-podman | 84.1-1.module_el8.10.0+4102+6c76e544 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:conmon | 3:2.1.10-1.module_el8.10.0+3970+8445edf6 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:container-selinux | 2:2.229.0-3.module_el8.10.0+4211+49ea0979 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:opentelemetry-collector | 0.144.0-2.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:podman | 7:5.8.2-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:podman-docker | 7:5.8.2-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:podman-plugins | 6:5.8.2-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:podman-remote | 7:5.8.2-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:podman-tests | 7:5.8.2-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| alpine:skopeo | 1.20.1-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:golang-github-go-jose-go-jose | 4.1.4-1 · Debian:14 | Package registry (OSV) |
| debian:golang-github-go-jose-go-jose.v3 | 3.0.5-1 · Debian:14 | Package registry (OSV) |
| Go:github.com/go-jose/go-jose/v3 | 3.0.5 | Package registry (OSV) |
| Go:github.com/go-jose/go-jose/v4 | 4.1.4 | Package registry (OSV) |
| opensuse:apptainer | 1.4.5-4.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:azure-storage-azcopy | 10.32.2-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:distribution | 3.1.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:google-guest-agent | 20260402.00-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:google-osconfig-agent | 20260330.00-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:grafana | 11.6.14+security01-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kyverno | 1.17.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:skopeo | 1.22.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:tekton-cli | 0.44.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:traefik | 3.6.15-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:traefik2 | 2.11.44-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:trivy | 0.70.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
+36
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-248 · Uncaught ExceptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- access.redhat.com/errata/RHSA-2026:21932
- access.redhat.com/errata/RHSA-2026:22258
- access.redhat.com/errata/RHSA-2026:22260
- github.com/go-jose/go-jose/security/advisories/GHSA-78h2-9frx-2jm8
- pkg.go.dev/github.com/go-jose/go-jose/v4#pkg-constants
- access.redhat.com/errata/RHSA-2026:10125
- access.redhat.com/errata/RHSA-2026:10130
- access.redhat.com/errata/RHSA-2026:10135
- access.redhat.com/errata/RHSA-2026:10175
- access.redhat.com/errata/RHSA-2026:11070
- access.redhat.com/errata/RHSA-2026:11217
- access.redhat.com/errata/RHSA-2026:11512
- access.redhat.com/errata/RHSA-2026:11688
- access.redhat.com/errata/RHSA-2026:11856
- access.redhat.com/errata/RHSA-2026:11916
- access.redhat.com/errata/RHSA-2026:11996
- access.redhat.com/errata/RHSA-2026:12116
- access.redhat.com/errata/RHSA-2026:12277
- access.redhat.com/errata/RHSA-2026:12279
Vendor advisories and official records. Exploit/PoC links are deliberately left out.