BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-34986High confidence

Go JOSE affect by a panic in JWE decryption

go-jose · go-jose

Official source article: GitHub GHSA-78H2-9FRX-2JM8 ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.65% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs go-jose go-jose and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

17 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 11 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communityskopeoVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.20.1-r0Alpine Security Database ↗Source updated 11 Sep 2026
Debian trixietrixie · sourcegolang-github-go-jose-go-joseAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian trixietrixie · sourcegolang-github-go-jose-go-jose.v3Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian trixietrixie · sourcegolang-gopkg-square-go-jose.v1Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian trixietrixie · sourcegolang-gopkg-square-go-jose.v2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcegolang-gopkg-square-go-jose.v1Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcegolang-gopkg-square-go-jose.v2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegolang-github-go-jose-go-joseVendor fix publishedDebian records a fixed source-package version for this release.4.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegolang-github-go-jose-go-jose.v3Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegolang-gopkg-square-go-jose.v1Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegolang-gopkg-square-go-jose.v2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegolang-github-go-jose-go-joseVendor fix publishedDebian records a fixed source-package version for this release.4.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegolang-github-go-jose-go-jose.v3Vendor fix publishedDebian records a fixed source-package version for this release.3.0.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegolang-gopkg-square-go-jose.v1Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegolang-gopkg-square-go-jose.v2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegolang-github-go-jose-go-joseUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegolang-gopkg-square-go-jose.v2Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges6 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/go-jose/go-joseSEMVER: introduced 0; last affected 2.6.3Not statedOSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/go-jose/go-jose/v3SEMVER: introduced 0; fixed 3.0.53.0.5OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/go-jose/go-jose/v4SEMVER: introduced 0; fixed 4.1.44.1.4OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/go-jose/go-jose<= 2.6.3Not statedGitHub advisory ↗upstream repository advisory · 6 Apr 2026
gogithub.com/go-jose/go-jose/v3< 3.0.53.0.5GitHub advisory ↗upstream repository advisory · 6 Apr 2026
gogithub.com/go-jose/go-jose/v4< 4.1.44.1.4GitHub advisory ↗upstream repository advisory · 6 Apr 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-19363

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

An exception is thrown from a function, but it is not caught.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

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.

Why

An exception is thrown from a function, but it is not caught.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Uncaught Exception → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-248 ↗

CWE-248: Uncaught Exception. An exception is thrown from a function, but it is not caught.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedDenial of serviceCWE-248
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-19363Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2929Splunk Splunk Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise ausnutzen, um beliebigen Code auszuführen, Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, SQL-Injection-, serverseitige Request-Forgery- und Cross-Site-Scripting-Angriffe durchzuführen, sensible Informationen offenzulegen oder zu manipulieren, Denial-of-Service-Zustände auszulösen oder andere, nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1268Red Hat Enterprise Linux (go-jose): Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1056Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-34514 Référence CVE CVE-2026-34515 https://www.cve.org/CVERecord?id=CVE-2026-34515 Référence CVE CVE-2026-34516 https://www.cve.org/CVERecord?id=CVE-2026-34516 Référence CVE CVE-2026-34517 https://www.cve.org/CVERecord?id=CVE-2026-34517 Référence CVE CVE-2026-34518 https://www.cve.org/CVERecord?id=CVE-2026-34518 Référence CVE CVE-2026-34519 https://www.cve.org/CVERecord?id=CVE-2026-34519 Référence CVE CVE-2026-34520 https://www.cve.org/CVERecord?id=CVE-2026-34520 Référence CVE CVE-2026-34525 https://www.cve.org/CVERecord?id=CVE-2026-34525 Référence CVE CVE-2026-34601 https://www.cve.org/CVERecord?id=CVE-2026-34601 Référence CVE CVE-2026-34986 https://www.cve.org/CVERecord?id=CVE-2026-34986 Référence CVE CVE-2026-35536 https://www.cve.org/CVERecord?id=CVE-2026-35536 Référence CVE CVE-2026-39883 https://www.cve.org/CVERecord?id=CVE-2026-39883 Référence CVE CVE-2026-40087 https://www.cve.org/CVERecord?id=CVE-2026-40087 Référence CVE CVE-2026-40460 https://www.cve.org/CVERecord?id=CVE-2026-40460 Référence CVE CVE-2026-40701 https://www.cve.org/CVERecord?id=CVE-2026-40701 Référence CVE CVE-2026-41066 https://www.cve.org/CVERecord?id=CVE-2026-41066 Référence CVE CVE-2026-42215 https://www.cve.org/CVERecord?id=CVE-2026-42215 Référence CVE CVE-2026-42284 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0888Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-28388 Référence CVE CVE-2026-28389 https://www.cve.org/CVERecord?id=CVE-2026-28389 Référence CVE CVE-2026-28390 https://www.cve.org/CVERecord?id=CVE-2026-28390 Référence CVE CVE-2026-29181 https://www.cve.org/CVERecord?id=CVE-2026-29181 Référence CVE CVE-2026-32280 https://www.cve.org/CVERecord?id=CVE-2026-32280 Référence CVE CVE-2026-32281 https://www.cve.org/CVERecord?id=CVE-2026-32281 Référence CVE CVE-2026-32283 https://www.cve.org/CVERecord?id=CVE-2026-32283 Référence CVE CVE-2026-32285 https://www.cve.org/CVERecord?id=CVE-2026-32285 Référence CVE CVE-2026-32287 https://www.cve.org/CVERecord?id=CVE-2026-32287 Référence CVE CVE-2026-34986 https://www.cve.org/CVERecord?id=CVE-2026-34986 Référence CVE CVE-2026-39836 https://www.cve.org/CVERecord?id=CVE-2026-39836 Référence CVE CVE-2026-39882 https://www.cve.org/CVERecord?id=CVE-2026-39882 Référence CVE CVE-2026-39883 https://www.cve.org/CVERecord?id=CVE-2026-39883 Référence CVE CVE-2026-42501 https://www.cve.org/CVERecord?id=CVE-2026-42501 Référence CVE CVE-2026-6914 https://www.cve.org/CVERecord?id=CVE-2026-6914 Référence CVE CVE-2026-6915 https://www.cve.org/CVERecord?id=CVE-2026-6915 Référence CVE CVE-2026-8053 https://www.cve.org/CVERecord?id=CVE-2026-8053 Référence CVE CVE-2026-8199 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0556Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2026-34515 Référence CVE CVE-2026-34516 https://www.cve.org/CVERecord?id=CVE-2026-34516 Référence CVE CVE-2026-34517 https://www.cve.org/CVERecord?id=CVE-2026-34517 Référence CVE CVE-2026-34518 https://www.cve.org/CVERecord?id=CVE-2026-34518 Référence CVE CVE-2026-34519 https://www.cve.org/CVERecord?id=CVE-2026-34519 Référence CVE CVE-2026-34520 https://www.cve.org/CVERecord?id=CVE-2026-34520 Référence CVE CVE-2026-34525 https://www.cve.org/CVERecord?id=CVE-2026-34525 Référence CVE CVE-2026-3479 https://www.cve.org/CVERecord?id=CVE-2026-3479 Référence CVE CVE-2026-3497 https://www.cve.org/CVERecord?id=CVE-2026-3497 Référence CVE CVE-2026-34986 https://www.cve.org/CVERecord?id=CVE-2026-34986 Référence CVE CVE-2026-35236 https://www.cve.org/CVERecord?id=CVE-2026-35236 Référence CVE CVE-2026-35237 https://www.cve.org/CVERecord?id=CVE-2026-35237 Référence CVE CVE-2026-35238 https://www.cve.org/CVERecord?id=CVE-2026-35238 Référence CVE CVE-2026-35239 https://www.cve.org/CVERecord?id=CVE-2026-35239 Référence CVE CVE-2026-35240 https://www.cve.org/CVERecord?id=CVE-2026-35240 Référence CVE CVE-2026-35469 https://www.cve.org/CVERecord?id=CVE-2026-35469 Référence CVE CVE-2026-3644 https://www.cve.org/CVERecord?id=CVE-2026-3644 Référence CVE CVE-2026-39883 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014026Go JOSE projectのGo JOSEにおけるキャッチされない例外に関する脆弱性

Go JOSEは、GoでJavaScriptのオブジェクト署名および暗号化の標準セットを実装しており、JSON Web Encryption（JWE）、JSON Web Signature（JWS）、およびJSON Web Token（JWT）の各標準をサポートしています。バージョン4.1.4および3.0.5より前では、algフィールドがキーラッピングアルゴリズム（A128GCMKW、A192GCMKW、A256GCMKWを除くKWで終わるもの）を示し、encrypted_keyフィールドが空の場合にJSON Web Encryption（JWE）オブジェクトの復号時にパニックが発生します。このパニックは、key_wrap.go内のcipher.KeyUnwrap()がencrypted_keyの長さに基づいて長さゼロまたは負のスライスを割り当てようとするときに発生します。このコードパスには、ParseEncrypted()、ParseEncryptedJSON()、ParseEncryptedCompact()のいずれかで解析し、その後に生成されたオブジェクトでDecrypt()を呼び出すことで到達できます。なお、解析関数は許容されるキーアルゴリズムのリストを受け取ります。もし許容されるキーアルゴリズムにキーラッピングアルゴリズムが含まれていなければ、解析は失敗し、アプリケーションに影響はありません。このパニックはまた、16バイト未満の任意の暗号文パラメータでcipher.KeyUnwrap()を直接呼び出すことでも発生しますが、この関数を直接呼び出すことはあまり一般的ではありません。このパニックはサービス拒否（DoS）につながる可能性があります。この脆弱性はバージョン4.1.4および3.0.5で修正されています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
go-jose: 4.0.0, < 4.1.4, < 3.0.5
Fixed
RHSA-2026:65906: Red Hat OpenShift Container Platform 4.12
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 6 Apr 2026 · Last source change 18 Sept 2026, 12:04 UTC · CWE-248 · Uncaught Exception

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-19363
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:65838; removed vendor advisory: access.redhat.com/RHSA-2026:65906; 1 further removals.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:65838 · 2 more references
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    security-advisories@github.com ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:65838; added vendor advisory: access.redhat.com/RHSA-2026:65906; 1 further additions.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:65838 · 2 more references
    security-advisories@github.com ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    go-jose: >= 4.0.0, < 4.1.4, < 3.0.5 · Fixed: RHSA-2026:62548: Red Hat OpenShift Container Platform 4.16
    After
    go-jose: >= 4.0.0, < 4.1.4, < 3.0.5 · Fixed: RHSA-2026:65906: Red Hat OpenShift Container Platform 4.12
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    go-jose: >= 4.0.0, < 4.1.4, < 3.0.5 · Fixed: RHSA-2026:17789: Cryostat 4 on RHEL 9
    After
    go-jose: >= 4.0.0, < 4.1.4, < 3.0.5 · Fixed: RHSA-2026:62548: Red Hat OpenShift Container Platform 4.16
    CNA ↗
  5. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:62548; removed vendor advisory: access.redhat.com/RHSA-2026:62550.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:62548 · 1 more references
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    security-advisories@github.com ↗
  6. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:62548; added vendor advisory: access.redhat.com/RHSA-2026:62550.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:62548 · 1 more references
    security-advisories@github.com ↗
  7. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:60023.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:60023
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    security-advisories@github.com ↗
  8. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:60023.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:60023
    security-advisories@github.com ↗
  9. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:60452.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:60452
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    security-advisories@github.com ↗
  10. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:60452.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:60452
    security-advisories@github.com ↗
  11. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:60444; removed vendor advisory: access.redhat.com/RHSA-2026:60449; 1 further removals.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:60444 · 2 more references
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    security-advisories@github.com ↗
  12. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:60444; added vendor advisory: access.redhat.com/RHSA-2026:60449; 1 further additions.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:60444 · 2 more references
    security-advisories@github.com ↗
  13. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 4.0.0, < 4.1.4; < 3.0.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    go-jose: >= 4.0.0, < 4.1.4, < 3.0.5 · Fixed: RHSA-2026:17789: Cryostat 4 on RHEL 9
    CNA ↗
  14. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    security-advisories@github.com ↗
  15. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:57590.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:57590
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    security-advisories@github.com ↗
  16. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:57590.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:57590
    security-advisories@github.com ↗
  17. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:56968; removed vendor advisory: access.redhat.com/RHSA-2026:57013.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:56968 · 1 more references
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    security-advisories@github.com ↗
  18. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:56968; added vendor advisory: access.redhat.com/RHSA-2026:57013.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:56968 · 1 more references
    security-advisories@github.com ↗
  19. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:54602; removed vendor advisory: access.redhat.com/RHSA-2026:56366; 1 further removals.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:54602 · 2 more references
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    security-advisories@github.com ↗
  20. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:54602; added vendor advisory: access.redhat.com/RHSA-2026:56366; 1 further additions.
    Before
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8
    After
    mitigation: github.com/GHSA-78h2-9frx-2jm8 · remediation: github.com/GHSA-78h2-9frx-2jm8 · vendor advisory: access.redhat.com/RHSA-2026:54602 · 2 more references
    security-advisories@github.com ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-19363↗CVE authority or vendor reference · GitHub GHSA-78H2-9FRX-2JM8↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-34986 · cve.blacktree.nl