CVE-2026-76101
keystore-go integrity and password check bypass in Decode()
Local attackers with file write access can strip a keystore's digest to skip checks and add trusted CA certificates.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche v3.0.3 | github.com/pavel-v-chernykh/keystore-go/v3 · -2308 d desde divulgación | |
| Divulgación | Publicada | CVE-2026-76101 divulgada · CVSS 7.1 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación PoC pública | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
The keystore-go library from pavlo-v-chernykh can be attacked by a local user with low privileges who has write access to a Java KeyStore file. By removing the file's trailing integrity digest, the attacker can bypass tamper detection and password verification, and add or replace trusted CA certificates without knowing the keystore password.
Affects legacy v2 versions of keystore-go before 3.0.0, where Decode() accepts a JKS keystore with its trailing integrity digest stripped. Fixed in 3.0.0.
Descripción original del registro (GitHub_M)
keystore-go is a Go implementation of the Java KeyStore encoder and decoder. In 2.1.0 and earlier, keystore.Decode in decoder.go does not check the error returned when reading the trailing SHA-1 integrity digest and bounds its comparison by the length of the digest actually read. If an attacker with write access removes the final 20-byte digest from a modified JKS file, the empty actual digest causes the comparison loop to execute zero times and Decode returns the parsed keystore without an error. For certificate-only stores using TrustedCertificateEntry values, this bypasses both tamper detection and password verification, allowing trusted CA certificates to be added or replaced without knowing the keystore password and potentially enabling interception or modification of TLS connections that trust the forged CA. This issue is fixed in version 3.0.0.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/pavel-v-chernykh/keystore-go |
Sin parche | — | — | v2.1.0+incompatible afectada |
gogithub.com/pavel-v-chernykh/keystore-go/v3 |
Corregida | v3.0.3 | -2308 d | v3.1.0 no afectada |
3.0.0v3.0.3Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/pavlo-v-chernykh/keystore-go/security/advisories/GHSA-j282-pjg5-j643https://github.com/pavlo-v-chernykh/keystore-go/commit/af93effd832cf1aef7794e69c31e1b668e17b851https://github.com/pavlo-v-chernykh/keystore-go/releases/tag/v3.0.0Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
