Skip to content

fabric-chaincode-java: TLS Private Key Password Disclosed in INFO Startup Logs in Chaincode-as-a-Service Mode

Moderate severity GitHub Reviewed Published May 14, 2026 in hyperledger/fabric-chaincode-java • Updated Jun 9, 2026

Package

maven org.hyperledger.fabric-chaincode-java:fabric-chaincode-shim (Maven)

Affected versions

>= 2.3.1, <= 2.5.9

Patched versions

2.5.10

Description

When chaincode is deployed in chaincode-as-a-service mode with TLS enabled, the chaincode server INFO level logging includes the TLS private key password in plaintext. An attacker with access to the chaincode server logs could recover the TLS private key password. If the attacker can also obtain the TLS private key, they could impersonate the chaincode server.

Recommendation

  • Update to the fixed version of the chaincode runtime.
  • Redact or remove existing logs that contain the TLS private key password.
  • Change the TLS private key password.

Mitigation

Impacted deployments can mitigate the vulnerability by restricting the logging level to WARNING or higher so that INFO level logs are not written.

References

@bestbeforetoday bestbeforetoday published to hyperledger/fabric-chaincode-java May 14, 2026
Published to the GitHub Advisory Database May 19, 2026
Reviewed May 19, 2026
Published by the National Vulnerability Database Jun 8, 2026
Last updated Jun 9, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(1st percentile)

Weaknesses

Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file. Learn more on MITRE.

CVE ID

CVE-2026-45581

GHSA ID

GHSA-wg5x-3g47-v38r

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.