CVE-2026-76101

7.1High

Published 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.1CVSS

High

0CVSS v3.110

Attack vector
Local
Complexity
Low
Privileges
Low
User action
None
Impact
High impact on confidentiality, integrity
Weakness
CWE-252, CWE-347, CWE-354

What an attacker gets

Local attackers can inject malicious CA certificates into JKS files by stripping the integrity digest. This bypasses password verification and allows for TLS interception.

Root cause

The decoder fails to verify the integrity digest and incorrectly treats a missing digest as a successful validation.

Affected versions

keystore-go versions 2.1.0 and earlier

CVSS v3.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Fix & remediation

Upgrade to version 3.0.0 or later. If you cannot upgrade, ensure that JKS files are stored in locations with strict write permissions to prevent unauthorized modification.

remediation — bash
$ go get github.com/pavlo-v-chernykh/keystore-go@v3.0.0

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-76101