GHSA-4w3g-jfj2-cw2q: Out-of-bounds Read

Published Oct 28, 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.

Affected Software

2 affected componentsFixes available
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

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. 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 28, 2026
Advisory Published
via GitHub·09:14 PM
Data Sourced
via GitHub·09:14 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

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

Applications using go-jose v3 or v4 are affected if they decrypt untrusted ciphertexts using A128CBC-HS256, A192CBC-HS384, or A256CBC-HS512 content-encryption algorithms.

2

What does an attacker need to do to trigger the issue?

An attacker needs to supply a crafted, untrusted ciphertext that is processed with one of the affected CBC-HMAC content-encryption modes. Insufficient parameter validation can cause the application to index an empty buffer and panic.

3

What mitigation is available if patching is not immediately possible?

For applications using github.com/go-jose/go-jose/v4 that do not require these CBC-HMAC modes, exclude A128CBC-HS256, A192CBC-HS384, and A256CBC-HS512 from the ContentEncryption algorithm list passed to ParseEncrypted, ParseEncryptedJSON, or ParseEncryptedCompact.

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