CVE-2026-89312EUVD-2026-108632GHSA-XX6H-2JGG-93M2
AesGcmCryptor.Open passes attacker-controlled nonce to cipher.AEAD.Open without length check, causing panic on wrong-size IV
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.0.0-rc4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The AesGcmCryptor component in a Go library that handles JSON Web Encryption (JWE) decryption is affected. A crafted JWE with an incorrectly sized initialization vector can cause the decrypting process to panic and crash, which may lead to denial of service for the application handling the input.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
`AesGcmCryptor.Open` passed a caller-supplied nonce straight to `cipher.AEAD.Open` without checking its length. The Go standard library panics rather than returning an error when a GCM nonce is not exactly `NonceSize()` bytes, so a JWE carrying a wrong-sized IV crashes the decrypting goroutine.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- github.com/ThalesGroup/gose
From 0.7.3 · through 0.13.0-rc1
- github.com/eclipse-keypont/gose
fixed in 1.0.0-rc4