Skip to main content
CVE-2026-76101VulnerabilityPublished

github.com/pavel-v-chernykh/keystore-go · keystore-go: Keystore integrity and password verification bypass via stripped trailing digest in Decode()

Affects github.com/pavel-v-chernykh/keystore-goSource GCVE Database

0
Compare
Authoritative record:CVE-2026-76101· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 3.0.0 soon.

Data as of 20 Nov 2026, 01:23 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.1
Patch
Available – fixed in 3.0.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade github.com/pavel-v-chernykh/keystore-go/v3 to 3.0.0.

Affected software

ProductAffectedFixed in
Gogithub.com/pavel-v-chernykh/keystore-goAffected
  • <=2.1.0
Fixed in–
Gogithub.com/pavel-v-chernykh/keystore-go/v3Affected
  • <3.0.0
Fixed in
  • 3.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to keystore-go version 3.0.0 or later, where this issue is fixed. The vendor advisory confirms that versions 3.x and 4.x are not impacted. No other mitigations are indicated since the fix is available.

Description

The keystore-go library versions up to 2.1.0 have a vulnerability in the Decode() function where the trailing SHA-1 integrity digest of a JKS keystore is not properly verified if the digest is stripped from the file. This allows an attacker with write access to a keystore file to remove the final 20 bytes, bypass integrity checks and password verification, and inject or replace trusted CA certificates silently. The issue is fixed in version 3.0.0.

References

Community reviews

Loading reviews…