CVE-2026-116585: Go JOSE: Panic during CBC-HMAC processing

Published Oct 26, 2026
·
Updated

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.

Other sources

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.

— Ubuntu

Go JOSE: Panic during CBC-HMAC processing

— Microsoft

Affected Software

30 affected componentsFixes available
Go JOSE Go JOSE<4.1.5
go/github.com/go-jose/go-jose/v3<=3.0.5
go/github.com/go-jose/go-jose/v4<4.1.5
4.1.5
ubuntu/golang-gopkg-square-go-jose.v2*
ubuntu/golang-gopkg-square-go-jose.v2*
ubuntu/golang-github-go-jose-go-jose*
ubuntu/golang-gopkg-square-go-jose.v2*
ubuntu/golang-github-go-jose-go-jose*
ubuntu/golang-github-go-jose-go-jose.v3*
ubuntu/golang-gopkg-square-go-jose.v2*
ubuntu/golang-github-go-jose-go-jose.v3*
ubuntu/golang-gopkg-square-go-jose.v2*
ubuntu/golang-github-go-jose-go-jose*
debian/golang-github-go-jose-go-jose<=4.0.5-1, <=4.1.4-2
debian/golang-github-go-jose-go-jose.v3<=3.0.3-6, <=3.0.5-1
debian/golang-gopkg-square-go-jose.v1<=1.1.2-4
debian/golang-gopkg-square-go-jose.v2<=2.6.0-2, <=2.6.3-3, <=2.6.3-4
debian/golang-github-go-jose-go-jose*
debian/golang-github-go-jose-go-jose*
debian/golang-github-go-jose-go-jose.v3*
debian/golang-github-go-jose-go-jose.v3*
debian/golang-gopkg-square-go-jose.v1*
debian/golang-gopkg-square-go-jose.v1*
debian/golang-gopkg-square-go-jose.v1*
All of the following
azurelinux/skopeo<1.14.4-16
1.14.4-16
Microsoft Azure Linux=3.0
All of the following
azurelinux/telegraf<1.31.0-37
1.31.0-37
Microsoft Azure Linux=3.0
All of the following
azurelinux/containerized-data-importer<1.62.0-10
1.62.0-10
Microsoft Azure Linux=3.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/go-jose/go-jose/v4 to a version that resolves this vulnerability.

    Fixed in 4.1.5
  2. Upgrade

    Upgrade azurelinux/skopeo to a version that resolves this vulnerability.

    Fixed in 1.14.4-16
  3. Upgrade

    Upgrade azurelinux/telegraf to a version that resolves this vulnerability.

    Fixed in 1.31.0-37
  4. Upgrade

    Upgrade azurelinux/containerized-data-importer to a version that resolves this vulnerability.

    Fixed in 1.62.0-10
  5. Upgrade

    Upgrade github.com/go-jose/go-jose/v4 to a version that resolves this vulnerability.

    Fixed in 4.1.5
  6. Configuration

    If CBC-HMAC modes are not required, do not include A128CBC-HS256, A192CBC-HS384, or A256CBC-HS512 in the ContentEncryption algorithms passed to ParseEncrypted, ParseEncryptedJSON, or ParseEncryptedCompact.

    github.com/go-jose/go-jose/v4 ContentEncryption algorithms = Exclude A128CBC-HS256, A192CBC-HS384, and A256CBC-HS512

Event History

Oct 26, 2026
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·09:06 PM
Data Sourced
via MITRE·09:06 PM
DescriptionWeakness
Data Sourced
via OSV·09:06 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Oct 28, 2026
Data Sourced
via OSV·08:15 PM
Affected Software
Advisory Published
via GitHub·09:14 PM
Data Sourced
via GitHub·09:14 PM
DescriptionWeaknessAffected Software
Oct 31, 2026
Data Sourced
via Microsoft·08:09 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this denial-of-service issue?

Applications are affected if they decrypt attacker-controlled JWE ciphertext using A128CBC-HS256, A192CBC-HS384, or A256CBC-HS512. The issue applies to Go JOSE versions before 4.1.5.

2

What must an attacker be able to do to trigger the problem?

An attacker needs to supply JWE ciphertext that the application attempts to decrypt with one of the affected CBC-HMAC content-encryption algorithms. An empty ciphertext buffer can reach unpadding and trigger a panic.

3

How can I determine whether my application is affected?

Review whether the application accepts untrusted JWE input for decryption and whether any of the three affected CBC-HMAC algorithms are enabled or used. Also check whether the Go JOSE version is earlier than 4.1.5.

4

What remediation is available?

Upgrade Go JOSE to version 4.1.5, which fixes the issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203