Skip to main content
Menu
CVEs

CVE

keystore-go integrity and password check bypass in Decode()

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.

CVE-2026-76101Published Updated Summary written by a model

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.0.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Attacker has write access to the keystore file

Summary

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.

Original 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.

Who should check

Teams running pavel-v-chernykh/keystore-go v2.1.0 or earlier to load JKS truststores with Decode(), especially those trusting CA certificates from a file an attacker could write.

Not fixed by: No fixed release exists on the bare module path; every release there predates the fix.

“Affected versions: github.com/pavel-v-chernykh/keystore-go ≤ v2.1.0+incompatible”

github.com

cve.now Index

12Pcve.now Index 12 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Attacker has write access to the keystore file
  • Upgrade to a fixed version: 3.0.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-76101 (keystore-go: Keystore integrity and password verification bypass via stripped trailing digest in Decode(), impacting legacy v2 versions), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-76101 (entry last updated 2026-11-18):
Affected:
- pavlo-v-chernykh keystore-go: fixed in 3.0.0
Fixed versions: 3.0.0.
Conditions (all must be true for the bug to be hit):
- Attacker has write access to the keystore file (source: https://github.com/pavlo-v-chernykh/keystore-go/security/advisories/GHSA-j282-pjg5-j643)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-76101 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76101 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/pavlo-v-chernykh/keystore-go/security/advisories/GHSA-j282-pjg5-j643
- https://github.com/pavlo-v-chernykh/keystore-go/commit/af93effd832cf1aef7794e69c31e1b668e17b851
- https://github.com/pavlo-v-chernykh/keystore-go/releases/tag/v3.0.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-76101
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-76101"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • pavlo-v-chernykh keystore-go

    fixed in 3.0.0

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · pavlo-v-chernykh/keystore-go · Advisory GHSA-j282-pjg5-j643
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-76101
RecordNVD · CVE-2026-76101
Other links 2
RepositoryGitHub · pavlo-v-chernykh/keystore-go · Commit af93effd
RepositoryGitHub · pavlo-v-chernykh/keystore-go · Release v3.0.0

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-76101

Is CVE-2026-76101 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Decode() in keystore-go does not require the keystore's trailing integrity digest, so the password check can be skipped when that digest is removed. An attacker who can write the JKS file but does not know the password can add or replace trusted CA certificates, which can enable man-in-the-middle interception of TLS connections that trust the forged CA.Source: github.com

Which versions are affected by CVE-2026-76101?

keystore-go: before 3.0.0.Source: cve.now feed data

Am I affected, and how do I check?

The legacy v2 versions of keystore-go before 3.0.0 are affected. To check, look at the keystore-go version in the project's go.mod file or dependency list.Source: github.com

How do I fix CVE-2026-76101?

Upgrade keystore-go to 3.0.0 or later, which is the fixed version.Source: github.com

More CVEs