Lucene search
+L

8 matches found

NVD
NVD
•added 2026/10/23 9:17 a.m.•5 views

CVE-2026-89317

gose parsed the JWS crit header into JwsHeader.Crit and then never read it. RFC 7515 §4.1.11 requires a recipient to reject a JWS whose listed critical extension parameters it does not understand. gose implements no header extensions, so every token carrying a non-empty crit should have been...

6.3CVSS0.00147EPSS
SaveExploits0References1
NVD
NVD
•added 2026/10/23 9:17 a.m.•4 views

CVE-2026-89320

HmacShaCryptor.Hash never hashed its input. For any input it returned HMACK"" — the MAC of the empty message under the key. Every AES-CBC-HMAC JWE produced or verified by gose therefore carried an authentication tag that is constant per key and independent of the message, removing ciphertext...

8.8CVSS0.00174EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/10/23 8:56 a.m.•5 views

EUVD-2026-108654

HmacShaCryptor.Hash never hashed its input. For any input it returned HMACK"" — the MAC of the empty message under the key. Every AES-CBC-HMAC JWE produced or verified by gose therefore carried an authentication tag that is constant per key and independent of the message, removing ciphertext...

8.8CVSS5.9AI score0.00174EPSS
SaveExploits0References1
CVE
CVE
•added 2026/10/23 8:56 a.m.•5 views

CVE-2026-89320

The gose library is vulnerable because the HmacShaCryptor.Hash function fails to hash its input, consistently returning HMAC_K("") (the MAC of an empty message). This flaw causes all AES-CBC-HMAC JWE tokens produced or verified by the library to carry an authentication tag that is constant for a ...

8.8CVSS5.9AI score0.00174EPSS
SaveExploits0References1
Cvelist
Cvelist
•added 2026/10/23 8:56 a.m.•12 views

CVE-2026-89320 HmacShaCryptor.Hash never hashes its input — returns constant HMAC_K("") for all inputs, voiding CBC-HMAC JWE integrity

HmacShaCryptor.Hash never hashed its input. For any input it returned HMACK"" — the MAC of the empty message under the key. Every AES-CBC-HMAC JWE produced or verified by gose therefore carried an authentication tag that is constant per key and independent of the message, removing ciphertext...

8.8CVSS0.00174EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/10/23 8:50 a.m.•5 views

EUVD-2026-108649

gose parsed the JWS crit header into JwsHeader.Crit and then never read it. RFC 7515 §4.1.11 requires a recipient to reject a JWS whose listed critical extension parameters it does not understand. gose implements no header extensions, so every token carrying a non-empty crit should have been...

6.3CVSS5.8AI score0.00147EPSS
SaveExploits0References1
CVE
CVE
•added 2026/10/23 8:50 a.m.•5 views

CVE-2026-89317

The gose library is vulnerable because JwtVerifierImpl.Verify fails to enforce the JWS crit header as required by RFC 7515 §4.1.11 . While the library correctly parses the crit header into JwsHeader.Crit, it fails to act on it. Since gose does not implement header extensions, any token containing...

6.3CVSS5.8AI score0.00147EPSS
SaveExploits0References1
Cvelist
Cvelist
•added 2026/10/23 8:50 a.m.•12 views

CVE-2026-89317 JwtVerifierImpl.Verify does not enforce the JWS `crit` header (RFC 7515 §4.1.11)

gose parsed the JWS crit header into JwsHeader.Crit and then never read it. RFC 7515 §4.1.11 requires a recipient to reject a JWS whose listed critical extension parameters it does not understand. gose implements no header extensions, so every token carrying a non-empty crit should have been...

6.3CVSS0.00147EPSS
SaveExploits0References1
Rows per page
Query Builder