Go JOSE: Panic during CBC-HMAC processing

TRUNG BÌNH 6.9CVE-2026-116585 · GHSA-4w3g-jfj2-cw2q · Công bố 26/10/2026 · cập nhật 31/10/2026

Tóm tắt nhanh

CVE-2026-116585 là lỗ hổng mức TRUNG BÌNH (CVSS 6.9) ảnh hưởng github.com/go-jose/go-jose/v3, github.com/go-jose/go-jose/v4.
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.26%, cao hơn 18.4% các lỗ hổng khác.
Cách xử lý: cập nhật lên 4.1.5 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
github.com/go-jose/go-jose/v3 Go	`≤ 3.0.5`	Chưa có bản vá
github.com/go-jose/go-jose/v4 Go	`< 4.1.5`	`4.1.5`

Mô tả

Summary

Decrypting a ciphertext with "A128CBC-HS256", "A192CBC-HS384", or "A256CBC-HS512" can result in a panic on untrusted input.

Note this advisory is the same as https://github.com/go-jose/go-jose/security/advisories/GHSA-6mp9-8xrw-74r4.

Details

Insufficient validation of parameters can lead to attempting to index into an empty buffer. See https://github.com/go-jose/go-jose/pull/292.

Workarounds

If the application does not require the CBC-HMAC modes for content encryption, and is using github.com/go-jose/go-jose/v4, do not include them in the list of ContentEncryption algorithms passed to ParseEncrypted / ParseEncryptedJSON / ParseEncryptedCompact.

Impact

Denial of service vulnerability. Any application which decrypts untrusted ciphertexts with the indicated algorithms is affected.

Acknowledgements

Thanks to Joshua Rogers of AISLE Research for reporting this problem.

Mô tả của NVD

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.5, decrypting untrusted JWE ciphertext with A128CBC-HS256, A192CBC-HS384, or A256CBC-HS512 can pass an empty ciphertext buffer to CBC-HMAC unpadding. Insufficient validation allows the empty buffer to be indexed, causing a panic and denial of service. Applications that decrypt attacker-controlled ciphertext with one of these content-encryption algorithms are affected. This issue is fixed in version 4.1.5.